[redhat-chai-bot]

Summary

Rebase all runtime container images from registry.access.redhat.com/ubi9/ubi-minimal to registry.access.redhat.com/ubi10/micro as part of the OCPSTRAT-3522 UBI10 migration initiative.

Changes

Updated the GO_RUNTIME ARG default in all 29 Dockerfiles under openshift/ci-operator/:

• 10 production image Dockerfiles in knative-images/ (activator, autoscaler, autoscaler-hpa, cleanup, controller, default-domain, migrate, queue, schema-tweak, webhook)
• 19 test image Dockerfiles in knative-test-images/ (autoscale, failing, grpc-ping, hellohttp2, hellovolume, helloworld, httpproxy, pizzaplanetv1, pizzaplanetv2, readiness, revisionfailure, runtime, servingcontainer, sidecarcontainer, singlethreaded, slowstart, timeout, volumes, wsserver)

Each Dockerfile's GO_RUNTIME ARG changed from:

ARG GO_RUNTIME=registry.access.redhat.com/ubi9/ubi-minimal

to:

ARG GO_RUNTIME=registry.access.redhat.com/ubi10/micro

No other changes were made. The GO_BUILDER ARG, build-image, and source-image Dockerfiles are unchanged.

Why this works

All affected Dockerfiles use a multi-stage build pattern where the runtime stage only copies a statically-linked Go binary and a LICENSE file — there are no RPM install steps (dnf/microdnf/yum) in any runtime stage. UBI10 micro is suitable because these containers need nothing beyond the binary and a minimal OS layer.

Validation

• grep -r 'ubi9' openshift/ci-operator/knative-images/ openshift/ci-operator/knative-test-images/ returns zero matches
• git diff --stat confirms exactly 29 files changed, 29 insertions, 29 deletions
• Only the GO_RUNTIME ARG line changed in each file

Jira

SRVKS-1371 (child of OCPSTRAT-3522)

---

AI-generated. Review for accuracy.

@crm00re requested from Slack

[openshift-ci-robot]

@redhat-chai-bot: This pull request references SRVKS-1371 which is a valid jira issue.

Details

In response to this:

Summary

Rebase all runtime container images from registry.access.redhat.com/ubi9/ubi-minimal to registry.access.redhat.com/ubi10/micro as part of the OCPSTRAT-3522 UBI10 migration initiative.

Changes

Updated the GO_RUNTIME ARG default in all 29 Dockerfiles under openshift/ci-operator/:

• 10 production image Dockerfiles in knative-images/ (activator, autoscaler, autoscaler-hpa, cleanup, controller, default-domain, migrate, queue, schema-tweak, webhook)
• 19 test image Dockerfiles in knative-test-images/ (autoscale, failing, grpc-ping, hellohttp2, hellovolume, helloworld, httpproxy, pizzaplanetv1, pizzaplanetv2, readiness, revisionfailure, runtime, servingcontainer, sidecarcontainer, singlethreaded, slowstart, timeout, volumes, wsserver)

Each Dockerfile's GO_RUNTIME ARG changed from:

ARG GO_RUNTIME=registry.access.redhat.com/ubi9/ubi-minimal

to:

ARG GO_RUNTIME=registry.access.redhat.com/ubi10/micro

No other changes were made. The GO_BUILDER ARG, build-image, and source-image Dockerfiles are unchanged.

Why this works

All affected Dockerfiles use a multi-stage build pattern where the runtime stage only copies a statically-linked Go binary and a LICENSE file — there are no RPM install steps (dnf/microdnf/yum) in any runtime stage. UBI10 micro is suitable because these containers need nothing beyond the binary and a minimal OS layer.

Validation

• grep -r 'ubi9' openshift/ci-operator/knative-images/ openshift/ci-operator/knative-test-images/ returns zero matches
• git diff --stat confirms exactly 29 files changed, 29 insertions, 29 deletions
• Only the GO_RUNTIME ARG line changed in each file

Jira

SRVKS-1371 (child of OCPSTRAT-3522)

---

AI-generated. Review for accuracy.

@crm00re requested from Slack

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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: redhat-chai-bot
Once this PR has been reviewed and has the lgtm label, please assign mvinkler 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:

• OWNERS

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

[openshift-ci]

Hi @redhat-chai-bot. Thanks for your PR.

I'm waiting for a openshift-knative member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[crm00re]

Testing a process. Will close in a moment.