Skip to content

ART-16004: Migrate golang v1.23.10 streams from quay.io to registry.redhat.io for OpenShift 4.19#10233

Open
lgarciaaco wants to merge 1 commit into
openshift-4.19from
ART-16004-migrate-golang-streams-4.19
Open

ART-16004: Migrate golang v1.23.10 streams from quay.io to registry.redhat.io for OpenShift 4.19#10233
lgarciaaco wants to merge 1 commit into
openshift-4.19from
ART-16004-migrate-golang-streams-4.19

Conversation

@lgarciaaco
Copy link
Copy Markdown
Contributor

@lgarciaaco lgarciaaco commented Apr 27, 2026

Summary

Migrate golang v1.23.10 streams from quay.io to registry.redhat.io for OpenShift 4.19.

Problem

Before: OpenShift 4.19 golang streams use quay.io/redhat-user-workloads registry
After: OpenShift 4.19 golang streams use registry.redhat.io/openshift/art-images-base registry

Build Details

Using different NVRs because the current ones don't pass conformance testing. This migration uses newer conformance-passing builds:

Build Reference: https://art-jenkins.apps.prod-stable-spoke1-dc-iad2.itup.redhat.com/job/aos-cd-builds/job/build%252Fgolang-builder/424/

RPM Versions:

  • golang-1.23.10-13.el8
  • golang-1.23.10-13.el9

Image Updates:

  • rhel-8-golang: v1.23.10-202603131509.p2.gdc331c7.el8 → v1.23.10-202604271455.p2.gdc331c7.el8
  • rhel-9-golang: v1.23.10-202603131509.p2.gd0321dd.el9 → v1.23.10-202604271455.p2.gbf0298b.el9

Related: ART-16004

…y.redhat.io

Support ART-16004 by migrating golang v1.23.10 builder images to registry.redhat.io for OpenShift 4.19.
The new images are newer builds (April 27 vs March 13) with same golang version, likely containing
security/stability improvements.

Updates:
- rhel-8-golang stream: quay.io/redhat-user-workloads/ocp-art-tenant/art-images:golang-builder-v1.23.10-202603131509.p2.gdc331c7.el8
  -> registry.redhat.io/openshift/art-images-base:openshift-golang-builder-container-v1.23.10-202604271455.p2.gdc331c7.el8
- rhel-9-golang stream: quay.io/redhat-user-workloads/ocp-art-tenant/art-images:golang-builder-v1.23.10-202603131509.p2.gd0321dd.el9
  -> registry.redhat.io/openshift/art-images-base:openshift-golang-builder-container-v1.23.10-202604271455.p2.gbf0298b.el9

rh-pre-commit: ART-16004

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
@openshift-ci openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 27, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 27, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 27, 2026

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Apr 27, 2026

@lgarciaaco: This pull request references ART-16004 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the sub-task to target the "4.19.z" version, but no target version was set.

Details

In response to this:

Change Description

Migration of golang v1.23.10 builder streams from quay.io to registry.redhat.io for OpenShift 4.19 release branch.

Files Changed

  • streams.yml: Updated rhel-8-golang and rhel-9-golang stream image references

Details

  • From: quay.io/redhat-user-workloads/ocp-art-tenant/art-images:golang-builder-v1.23.10-202603131509.*
  • To: registry.redhat.io/openshift/art-images-base:openshift-golang-builder-container-v1.23.10-202604271455.*
  • Versions: Same golang v1.23.10, updated builds (March 13 → April 27, 2026)
  • Architectures: Both RHEL 8 and RHEL 9 golang builders updated

Testing

This change affects golang builder streams used for OpenShift 4.19 builds. The migration uses newer builds of the same golang version (v1.23.10) from the official Red Hat registry.

JIRA

Related to: ART-16004

Risk Assessment

Low Risk: Same golang version, same functionality, newer build timestamp, official registry migration.

Instructions 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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 27, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign sosiouxme for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@lgarciaaco
Copy link
Copy Markdown
Contributor Author

/hold for controlled merging

@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 27, 2026
@lgarciaaco lgarciaaco marked this pull request as ready for review April 29, 2026 09:36
@openshift-ci openshift-ci Bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 29, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 29, 2026

@lgarciaaco: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/art-pre-commit-check e0ba934 link false /test art-pre-commit-check

Full PR test history. Your PR dashboard.

Details

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants