chore(base-image): Konflux builds to UBI9/RHEL9 #2780
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Updated all Konflux build configuration to use UBI9 and RHEL 9: - konflux.Dockerfile: Updated base images to UBI9 - Builder stage: registry.access.redhat.com/ubi9/ubi:latest - Final stage: registry.access.redhat.com/ubi9/ubi-minimal:latest - Added Cachi2 environment sourcing for hermetic builds - Updated image label from rhacs-collector-rhel8 to rhacs-collector-rhel9 - rpms.in.yaml: Changed context from bare:true to UBI9 image - Uses registry.access.redhat.com/ubi9/ubi:latest as base - Reduces package resolution scope - rpms.rhel.repo: Updated repository URLs from RHEL 8 to RHEL 9 - Changed baseurl from rhel8/8 to rhel9/9 - Updated repo names from rhel-8-for to rhel-9-for - .tekton/collector-build.yaml: Updated CPE label from el8 to el9 - rpms.lock.yaml: Deleted RHEL 8 lockfile - Konflux will auto-generate RHEL 9 lockfile on first hermetic build - New lockfile will be committed after successful first build This change enables hermetic builds with RHEL 9 packages for all architectures (aarch64, ppc64le, s390x, x86_64). User request: "reach over into the ../collector repository and begin a new branch and start working on updating the konflux build there to be using ubi9/rhel9 like we did here [in stackrox]" Co-Authored-By: Claude Sonnet 4.5 <[email protected]>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #2780 +/- ##
=======================================
Coverage 27.38% 27.38%
=======================================
Files 95 95
Lines 5427 5427
Branches 2548 2548
=======================================
Hits 1486 1486
Misses 3214 3214
Partials 727 727
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Cannot generate rpms.lock.yaml locally due to Red Hat CDN SSL certificate issues in Docker container. Disabling hermetic builds temporarily to allow UBI9 migration testing. Will re-enable hermetic builds once lockfile can be generated properly. Co-Authored-By: Claude Sonnet 4.5 <[email protected]>
Author
|
/retest |
This completes the UBI9/RHEL9 migration for collector Konflux builds, matching the approach used in stackrox repository. Changes: - Generated rpms.lock.yaml for RHEL 9 (4,668 lines, all 4 architectures) - Updated rpms.in.yaml: clang-19.1.7→clang, bare:true→image context - Updated .tekton/collector-build.yaml: re-enabled hermetic builds, CPE label el8→el9 - Updated rpms.rhel.repo: RHEL 8→9 repository configurations The RPM lockfile was generated using rpm-lockfile-prototype with Red Hat subscription credentials via update.repos.sh script (kept locally only). Hermetic builds are required to access RHEL-only development packages (elfutils-libelf-devel, tbb-devel, c-ares-devel) that aren't available in public UBI repositories. AI-assisted commit
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
A detailed explanation of the changes in your PR.
Feel free to remove this section if it is overkill for your PR, and the title of your PR is sufficiently descriptive.
Checklist
Automated testing
If any of these don't apply, please comment below.
Testing Performed
TODO(replace-me)
Use this space to explain how you tested your PR, or, if you didn't test it, why you did not do so. (Valid reasons include "CI is sufficient" or "No testable changes")
In addition to reviewing your code, reviewers must also review your testing instructions, and make sure they are sufficient.
For more details, ref the Confluence page about this section.