-
Story
-
Resolution: Done
-
Normal
-
s2i-1.4
-
None
-
2
-
False
-
None
-
False
-
KONFLUX-2279 - Source-to-Image enablement
-
s2i updated to use go 1.20 for compilation, and ubi9-minimal as its base image.
-
Enhancement
-
Proposed
-
-
-
Builds Sprint #5
Story (Required)
As a Red Hat engineer trying to build s2i on Konflux I want s2i to use official Red Hat container catalog images in its build process.
<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>
s2i currently uses OpenShift CI images in its upstream build process. Konflux can't pull these images by default because they require a separate pull secret. We can build using the equivalent UBI go-toolset images.
Out of scope
<Defines what is not included in this story>
- Release with Konflux
- Run tests on Konflux
- Update to golang 1.21
Approach (Required)
<Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>
- Update the Dockerfiles for s2i to reference the UBI9 go-toolset images
- Merge upstream and re-run the "simple" build on Konflux.
Dependencies
<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>
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>
- Simple "onboarding" build on Konflux succeeds.
- Go toolset from UBI9 is used as the base of the build.
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