updating openshift-preflight build image to go 1.26.3#80109
Conversation
Signed-off-by: Adam D. Cornett <adc@redhat.com>
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: acornett21 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 |
WalkthroughThis PR updates the OpenShift preflight CI operator configurations to use Golang 1.26 instead of 1.25. The same image stream tag field is updated identically across three parallel release branch configurations (4.13, 4.21, and 4.22), changing the builder image from ChangesPreflight Go toolchain version update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Suggested labels
Suggested reviewers
🚥 Pre-merge checks | ✅ 15✅ Passed checks (15 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
[REHEARSALNOTIFIER]
Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals. Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
/pj-rehearse pull-ci-redhat-openshift-ecosystem-openshift-preflight-main-4.13-e2e pull-ci-redhat-openshift-ecosystem-openshift-preflight-main-4.13-images pull-ci-redhat-openshift-ecosystem-openshift-preflight-main-4.22-e2e pull-ci-redhat-openshift-ecosystem-openshift-preflight-main-4.22-images pull-ci-redhat-openshift-ecosystem-openshift-preflight-main-4.21-e2e pull-ci-redhat-openshift-ecosystem-openshift-preflight-main-4.21-images |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In
`@ci-operator/config/redhat-openshift-ecosystem/openshift-preflight/redhat-openshift-ecosystem-openshift-preflight-main__4.13.yaml`:
- Line 8: The tag rhel-9-release-golang-1.26-openshift-4.23 is invalid; replace
that tag value with the correct promoted OCP 4.23 Go image tag that actually
provides Go 1.26.3 (i.e., update the tag: field value to the promoted release
tag), then validate the resolved image exists (oc get istag release:<new-tag>)
and confirm the image contains Go 1.26.3 (pull/run the image or inspect with oc
debug/pod and run go version) before committing.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml
Review profile: CHILL
Plan: Enterprise
Run ID: bbcab140-8bc9-4818-9ce9-9ef55cdb16eb
📒 Files selected for processing (3)
ci-operator/config/redhat-openshift-ecosystem/openshift-preflight/redhat-openshift-ecosystem-openshift-preflight-main__4.13.yamlci-operator/config/redhat-openshift-ecosystem/openshift-preflight/redhat-openshift-ecosystem-openshift-preflight-main__4.21.yamlci-operator/config/redhat-openshift-ecosystem/openshift-preflight/redhat-openshift-ecosystem-openshift-preflight-main__4.22.yaml
| name: release | ||
| namespace: openshift | ||
| tag: rhel-9-release-golang-1.25-openshift-4.23 | ||
| tag: rhel-9-release-golang-1.26-openshift-4.23 |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify the image stream tag exists in the cluster
echo "Checking if image stream tag exists..."
oc get istag release:rhel-9-release-golang-1.26-openshift-4.23 -n openshift 2>/dev/null || echo "Image stream tag not found in default cluster"
echo -e "\n Checking related tags in the release image stream..."
oc get imagestream release -n openshift -o json 2>/dev/null | jq -r '.spec.tags[]? | select(.name | contains("golang-1.26")) | .name' || echo "Could not query image stream"Repository: openshift/release
Length of output: 201
🌐 Web query:
OpenShift image stream golang 1.26 rhel-9-release-golang-1.26-openshift-4.23 registry
💡 Result:
As of June 4, 2026, the specific image stream tag rhel-9-release-golang-1.26-openshift-4.23 is not a standard, publicly documented component in the OpenShift Container Platform registry ecosystem [1][2]. OpenShift manages container images through image streams, typically located in the openshift namespace [1]. While OpenShift releases utilize specific builder images (e.g., registry.ci.openshift.org/ocp/builder:rhel-9-golang-1.25-openshift-4.22) for their internal CI/CD processes [3], the naming convention for these tags generally follows the pattern rhel-9-release-golang-X.Y-openshift-Z.W. Current OpenShift releases (such as version 4.23, which is in active CI/nightly development as of June 2026) [4] follow updated golang versions. If you are looking for a specific builder image, you should check the official Red Hat Ecosystem Catalog or the internal image streams of your cluster using: oc get istag -n openshift This command will list all available image stream tags in your cluster, confirming whether the specific golang 1.26 tag is available in your environment [5]. If it is not present, it may indicate that the platform has not yet migrated to that specific Go version for its official builder images or that the image has not been promoted to the standard registry [1].
Citations:
- 1: https://docs.redhat.com/en/documentation/openshift_container_platform/4.16/html-single/images/index
- 2: https://docs.openshift.com/container-platform/4.15/registry/index.html
- 3: openshift/service-ca-operator@de11f78
- 4: https://openshift-release.apps.ci.l2s4.p1.openshiftapps.com/
- 5: https://docs.redhat.com/en/documentation/openshift_container_platform/4.14/html/images/managing-image-streams
Update the Go 1.26.3 image stream tag reference (tag is missing / can’t be trusted)
In ci-operator/config/redhat-openshift-ecosystem/openshift-preflight/redhat-openshift-ecosystem-openshift-preflight-main__4.13.yaml (line 8), the referenced tag: rhel-9-release-golang-1.26-openshift-4.23 does not exist in the openshift namespace (oc get istag release:rhel-9-release-golang-1.26-openshift-4.23 returns not found). Replace it with the correct promoted tag for the OCP 4.23 release, then validate the resolved image contents actually provide the Go 1.26.3 toolchain (the tag name alone doesn’t encode the patch version).
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In
`@ci-operator/config/redhat-openshift-ecosystem/openshift-preflight/redhat-openshift-ecosystem-openshift-preflight-main__4.13.yaml`
at line 8, The tag rhel-9-release-golang-1.26-openshift-4.23 is invalid; replace
that tag value with the correct promoted OCP 4.23 Go image tag that actually
provides Go 1.26.3 (i.e., update the tag: field value to the promoted release
tag), then validate the resolved image exists (oc get istag release:<new-tag>)
and confirm the image contains Go 1.26.3 (pull/run the image or inspect with oc
debug/pod and run go version) before committing.
|
@acornett21: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse pull-ci-redhat-openshift-ecosystem-openshift-preflight-main-4.13-e2e |
|
@acornett21: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse pull-ci-redhat-openshift-ecosystem-openshift-preflight-main-4.13-e2e |
|
@acornett21: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse pull-ci-redhat-openshift-ecosystem-openshift-preflight-main-4.13-e2e |
|
@acornett21: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
@acornett21: 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. |
|
/pj-rehearse ack |
|
@acornett21: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
Summary by CodeRabbit