Epic Goal

Transition all ACM 2.13 Prow CI jobs to Konflux, enabling the team to build, test, and deliver services within the Konflux CI/CD environment as the standard.

Why is this important?

Migrating to Konflux aligns with the broader strategy for CI/CD standardization across teams. This shift is crucial for:

• Ensuring consistency, stability, and reliability in the release pipeline.
• Gaining access to improved tooling available in Konflux.

Scenarios

...

Acceptance Criteria

• [ ] Prow CI jobs for ACM 2.13 are successfully migrated to Konflux.

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions:

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Doc issue opened with a completed template. Separate doc issue
  opened for any deprecation, removal, or any current known
  issue/troubleshooting removal from the doc, if applicable.