Bump OCP and go for OSC 1.13 - #81818
Conversation
Signed-off-by: Julien Ropé <jrope@redhat.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
WalkthroughThe development CI configuration for the sandboxed-containers-operator is updated from OpenShift 4.21 to 4.22 across its base image, build root image, and release integration references. ChangesOpenShift 4.22 CI Configuration
Estimated code review effort: 1 (Trivial) | ~2 minutes 🚥 Pre-merge checks | ✅ 15✅ Passed checks (15 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
openshift-ci
Bot
added
the
approved
|
[REHEARSALNOTIFIER]
A total of 61 jobs have been affected by this change. The above listing is non-exhaustive and limited to 25 jobs. A full list of affected jobs can be found here Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
/pj-rehearse |
|
@littlejawa: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/approve /lgtm |
|
/retest |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: beraldoleal, dbkreling, littlejawa The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/rehearsals-ack |
|
/pj-rehearse ack |
|
@dbkreling: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
openshift-merge-bot
Bot
added
the
rehearsals-ack
|
@littlejawa: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
PR #81818 bumped the Go builder from 1.25/4.21 to 1.26/4.22, but the image ocp/builder:rhel-9-golang-1.26-openshift-4.22 does not exist. The Go 1.26 builder is published under the 4.23 tag, as used by other projects (loki, rosa, odf-operator, etc.). This fixes all Prow CI jobs for sandboxed-containers-operator which are currently failing with "image not found". Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Go 1.26 (set in #81818 and corrected in #81857) causes go mod tidy failures because it bumps major k8s dependencies (api/apimachinery from v0.34 to v0.35, controller-runtime from v0.22 to v0.23) which is unsafe on the release branch. Use rhel-9-golang-1.25-openshift-4.22 instead, which provides Go 1.25.x compatible with go.mod's "go 1.25.7" directive and avoids any dependency churn. Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Signed-off-by: Julien Ropé <jrope@redhat.com>
PR openshift#81818 bumped the Go builder from 1.25/4.21 to 1.26/4.22, but the image ocp/builder:rhel-9-golang-1.26-openshift-4.22 does not exist. The Go 1.26 builder is published under the 4.23 tag, as used by other projects (loki, rosa, odf-operator, etc.). This fixes all Prow CI jobs for sandboxed-containers-operator which are currently failing with "image not found". Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Go 1.26 (set in openshift#81818 and corrected in openshift#81857) causes go mod tidy failures because it bumps major k8s dependencies (api/apimachinery from v0.34 to v0.35, controller-runtime from v0.22 to v0.23) which is unsafe on the release branch. Use rhel-9-golang-1.25-openshift-4.22 instead, which provides Go 1.25.x compatible with go.mod's "go 1.25.7" directive and avoids any dependency churn. Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
3 participants
Summary by CodeRabbit
Updates the sandboxed-containers-operator development CI configuration to use OpenShift 4.22, including its base image, build environment, and initial/latest release integration images.