skills.rest
konflux-ci
konflux-ciOFFICIAL
Explore all skills by this author →
GitHub

understanding-konflux-resources

Map user questions to the correct Konflux resource and namespace placement.

8|12|Updated Nov 7, 2025
Search Tags:#resources#RPA#namespace#konflux#RP#ITS#cross-namespace
One-click install
npx skills add https://github.com/konflux-ci/skills --skill understanding-konflux-resources
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: understanding-konflux-resources
Source: https://github.com/konflux-ci/skills/tree/main/skills/understanding-konflux-resources
Command: npx skills add https://github.com/konflux-ci/skills --skill understanding-konflux-resources

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill clarifies Konflux resource semantics, who creates which resource, and where they belong (tenant vs managed namespaces). It reduces misconfigurations and cross-namespace confusion.

Core Features & Use Cases

  • Quick reference for Konflux CRs: Application, Component, Snapshot, IntegrationTestScenario, ReleasePlan, ReleasePlanAdmission
  • Clear guidance on namespace placement (tenant vs managed) and who creates each resource
  • Real-world examples of cross-namespace references and lifecycle

Quick Start

Review the quick reference table to decide which Konflux resource to create for your workflow (RP in tenant, RPA in managed, etc.).

Frequently Asked Questions about understanding-konflux-resources

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose between Application, Component, and Snapshot in Konflux?▼

Application is the top-level resource representing your project; Component defines individual workloads within it; Snapshot captures a versioned set of built Components. Each serves a distinct lifecycle stage in your Konflux workflow.

What's the difference between ReleasePlan and ReleasePlanAdmission, and where do they belong?▼

ReleasePlan is created in tenant namespaces and defines release targets; ReleasePlanAdmission is created in managed namespaces and grants permission to release. Together they enforce cross-namespace release governance.

When should I use IntegrationTestScenario in Konflux?▼

IntegrationTestScenario defines automated tests that validate your built Snapshots before release. Use it to ensure quality gates across your release pipeline in managed namespaces.

How do tenant and managed namespaces differ in Konflux resource placement?▼

Tenant namespaces hold Application and Component definitions created by users; managed namespaces hold system-created resources like ReleaseAdmissions and test infrastructure. This separation enforces security and lifecycle boundaries.

Can Konflux resources reference other resources across namespaces?▼

Yes. ReleasePlan references ReleasePlanAdmission, Snapshot references Components, and cross-namespace references are supported through formal resource links, enabling multi-tenant release workflows.

What causes common Konflux resource misconfigurations?▼

Placing RP or RPA in the wrong namespace, unclear ownership of resource creation, and incorrect cross-namespace references are common issues. Reference the resource placement guide to align with tenant vs. managed namespace semantics.

Related Skills

Explore More Education & Research Skills→
camoneartcamoneart
5

k8s-security-policies

Implement Kubernetes NetworkPolicy, PodSecurityPolicy, and RBAC configurations.

Community
Advanced
happier-devhappier-dev
1.4k

happier-release-promote

Promote validated release candidates across preview and production lanes after explicit human approval.

Official
Advanced
dmzoneilldmzoneill
2

check-integration-tests

Check Konflux integration test status and retrieve failed test results.

Community
Intermediate
foxj77foxj77
18

k8s-platform-tenancy

Provision multi-tenant Kubernetes namespaces with RBAC, quotas, and network policies.

Community
Advanced