Konflux Resource Deployment
How Konflux resources are defined and deployed across repositories
Konflux resources for container images are split between two repositories:
- containers: Per-image resources generated from
properties.yml - infrastructure: Application-level resources and deployment to the Konflux cluster
This separation allows independent iteration on each concern.
Deployment Matrix
| Resource Type | Source | Containers MR | Containers Push | Infra MR | Infra Push |
|---|---|---|---|---|---|
| Component | containers | manual | manual | - | - |
| ImageRepository | containers | manual | manual | - | - |
| ReleasePlanAdmission | containers | - | automatic | manual | automatic |
| EnterpriseContractPolicy | containers | - | automatic | manual | automatic |
| IntegrationTestScenario | containers | - | automatic | manual | automatic |
| Application | infrastructure | - | - | manual | automatic |
| ReleasePlan | infrastructure | - | - | manual | automatic |
| ServiceAccount, Secret | infrastructure | - | - | manual | automatic |
Legend:
- Containers MR: Downstream pipeline triggered from containers MR (deploys from MR commit)
- Containers Push: Downstream pipeline triggered from containers push to main
- Infra MR: Infrastructure MR pipeline (manual trigger)
- Infra Push: Infrastructure push to main or web pipeline
Resource Locations and Rationale
Containers Repo
Resources are defined in konflux-templates/ and rendered to konflux-templates/rendered.yml.
Component and ImageRepository:
- Ownership: Components are managed by the containers repo. The infrastructure pipeline uses
ONLY_DOWNSTREAMso only explicit downstream triggers from containers deploy changes, giving the containers repo full control over the component lifecycle. - Dynamic generation: Generated from
images/*/properties.ymlviaci/internal/generate_konflux_resources.sh, depending on per-image configuration (variants, tags, repository names). - Timing: Must be deployed early during MR review so Konflux can build and test new images.
ReleasePlanAdmission:
- Dynamic generation: Includes per-image tag mappings extracted from
properties.yml. - Main branch only: Prevents race conditions—deploying from a feature branch risks undoing other images’ onboarding. If branch A adds image-foo and branch B (created earlier) adds image-bar, deploying B’s RPA would remove image-foo from the release config.
EnterpriseContractPolicy:
- Documentation co-location: Policy exclusions are documented in Image Pipeline. Keeping policy and documentation together eases maintenance.
IntegrationTestScenario:
- Ownership co-location: Scenarios live alongside the components,
tests-k8s.ymlinventory, and trigger manifests that describe them. Config is split between per-type CR templates (konflux-templates/scenarios/<type>.yml.j2, owning all params and resolver refs) and a pure application/trigger matrix (konflux-templates/scenarios.yml). Both the CR renderer (konflux-templates/rendered.yml) and the trigger-manifest generator read the same config, so deployed scenarios and manifest expectations cannot drift apart. See the trigger manifests reference for the manifest schema. - Deployment: Deployed through the
*-releasessync (fetchesrendered.ymlfrom the main branch on every merge to main), not the*-componentssync. The components sync deploys from MR-head SHAs, so concurrent or stale MR pipelines would reset the live ITS CR to an older version; ITS is static config that is not supposed to change in MRs. The releases sync avoids this race and also means Renovate bundle-digest and IMAGE_TAG bumps auto-deploy on merge without any manual step. - Renovate: Bundle digest and IMAGE_TAG pins are managed by regex managers in this repo’s
renovate.json.
Infrastructure Repo
Application and ReleasePlan are defined in kubernetes/containers-*/ directories (one per
Konflux application):
- Independent iteration: Changes are decoupled from containers repo activity—they can be modified, test-deployed via manual trigger in an infrastructure MR, verified, and merged without touching the containers repo.
- Testable before merge: If defined in the containers repo, these would only deploy after merging to main (like RPAs), making iteration difficult.
- Static configuration: These resources don’t depend on per-image data from
properties.yml.
ServiceAccount and Secret for releases are defined in
kubernetes/release-quay-hummingbird*/ directories (one per Quay organization):
- Security: Secret specifications (names, structure, credential references) should not be exposed in the containers repo.
- Independent iteration: Like other infrastructure resources, these can be modified and test-deployed without touching the containers repo.
The service accounts are referenced by ReleasePlanAdmissions to authorize pushing images to
each quay.io/hummingbird* organization.
See Also
- Image Pipeline – Build, test, and release stages