What is the difference between an Application and a Component in Konflux?

An Application is a logical label used to group related services together, while a Component defines the actual build configuration and Git source for an individual repository.

Where should I place my ReleasePlan resource?

The ReleasePlan (RP) belongs in the Tenant namespace (your workspace), while the ReleasePlanAdmission (RPA) belongs in the Managed namespace controlled by the platform team.

What is the naming convention for Konflux Custom Resources?

Resources must be written without spaces using PascalCase, such as IntegrationTestScenario, ReleasePlan, and ReleasePlanAdmission.

Is the ReleasePlanAdmission (RPA) created automatically?

No. A common misconception is that RPA is auto-generated. It must be manually created by a Platform Engineer in the managed namespace to define release pipelines and credentials.

How are Snapshots handled in Konflux?

Snapshots are immutable sets of component artifacts that are automatically created by the Integration Service after a successful build; you should not create them manually.

Konflux Resource Guide

Name: Konflux Resource Guide
Author: konflux-ci

bykonflux-ci

•

Deployment & DevOps

Navigates and clarifies the structure, ownership, and namespace placement of Konflux Kubernetes Custom Resources for efficient CI/CD workflows.

About

This skill provides a comprehensive reference for the Kubernetes Custom Resources (CRs) used within Konflux. It helps developers and platform engineers distinguish between resources they must create (like Applications and ReleasePlans) and those Konflux generates automatically (like Snapshots). By enforcing strict naming conventions and clarifying the boundary between Tenant and Managed namespaces, this skill prevents common configuration errors and hallucinations regarding automated resource creation.

Key Features

Maps CI/CD workflows to specific namespace placements (Tenant vs. Managed)
Provides strict naming convention enforcement for resources like IntegrationTestScenario and ReleasePlan
Identifies common hallucinations regarding ReleasePlanAdmission and Snapshot automation
Clarifies ownership roles for all Konflux resources (User vs. Platform Engineer vs. Auto-generated)
Explains the hierarchical relationship between Applications and Components
6 GitHub stars

Use Cases

Troubleshooting 'resource not found' or namespace configuration errors
Mapping existing CI/CD pipelines to Konflux-specific Custom Resources
Architecting multi-repo applications for release within Konflux

About

Key Features

Maps CI/CD workflows to specific namespace placements (Tenant vs. Managed)
Provides strict naming convention enforcement for resources like IntegrationTestScenario and ReleasePlan
Identifies common hallucinations regarding ReleasePlanAdmission and Snapshot automation
Clarifies ownership roles for all Konflux resources (User vs. Platform Engineer vs. Auto-generated)
Explains the hierarchical relationship between Applications and Components
6 GitHub stars

Use Cases

Troubleshooting 'resource not found' or namespace configuration errors
Mapping existing CI/CD pipelines to Konflux-specific Custom Resources
Architecting multi-repo applications for release within Konflux