Story (Required)

As a developer trying to use s2i to build container images I want a UBI9 based image so that I can deploy it on OpenShift 4.16+ clusters.

<Describes high level purpose and goal for this story. Answers the questions: Who is impacted, what is it and why do we need it? How does it improve the customer’s experience?>

Background (Required)

<Describes the context or background related to this story>

OCP 4.16 is based on UBI9/RHEL9. Producing UBI9 based images ensures we have full kernel level compatibility between host and container environments.

Out of scope

<Defines what is not included in this story>

• Golang 1.22
• FIPS support
• Updating tasks, build strategies to use UBI9-based image.
• Producing RHEL 10 based image.

Approach (Required)

<Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>

• Create new CPE ID for rhel9 variant of source-to-image Spun out to BUILD-1318
• Create new Comet repository for s2i rhel9 Spun out to BUILD-1319
• Create rhel9 variant Containerfile for s2i Spun out to BUILD-1317
• Create new rhel9 component in Konflux for s2i. May also need to rename/re-onboard the rhel8 component. Spun out to BUILD-1317

Dependencies

<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

• Go toolset for RHEL9

Acceptance Criteria (Mandatory)

<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>

• rhel9 variant for s2i set up in Konflux, passing EC checks.
• CPE set up and approved for rhel9 variant (needs coordination with product security)
• Comet repository set up for s2i rhel9 image.

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