Story (Required)

As a developer trying to build and release s2i RHEL9 image I want use Konflux for the CI

Background (Required)

S2i container currently run on RHEL8 base image, and user want to run that on RHEL9. Also RHEL8 will go out of maintenance soon.

Out of scope

• Testing
• Code changes

Approach (Required)

• Create a Containerfile in openshift/source-to-image for UBI9/RHEL9 based image. (Dockerfile.rhel8, Dockerfile.rhel9)
• Create a component under application ocp-tools-s2i woprkspace under application "Source To Image". Use the configuration as code approach. https://konflux-ci.dev/docs/building/configuration-as-code/
• Create RPA, Integration test scenarios and Release in Konflux release config repo.

https://konflux.pages.redhat.com/docs/users/releasing/preparing-for-release.html

Dependencies

• Comet repositories are present
• CPE ID is created

Acceptance Criteria (Mandatory)

• Konflux should build S2I on RHEL9 base image
• All EC checks should pass
• Konflux RPA and cluster configs created

<Describe edge cases to consider when implementing the story and defining tests>

<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

Legend

Unknown

Verified

Unsatisfied

Done Checklist

• Code is completed, reviewed, documented and checked in
• Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
• Continuous Delivery pipeline(s) is able to proceed with new code included
• Customer facing documentation, API docs etc. are produced/updated, reviewed and published
• Acceptance criteria are met