Use QCI pull-through proxy for CI image references

[redhat-chai-bot]

Summary

Migrate Dockerfile FROM references from registry.ci.openshift.org to the QCI pull-through proxy (quay-proxy.ci.openshift.org/openshift/ci).

Details

• Dockerfile.ocp:6: FROM registry.ci.openshift.org/ocp/5.0:cli → FROM quay-proxy.ci.openshift.org/openshift/ci:ocp_5.0_cli
• Image verified pullable via skopeo inspect before updating
• builder and base-rhel* images are excluded (ART-managed)
• This is a test PR to verify the QCI pull-through proxy works correctly in CI builds before rolling out to remaining payload repos

---

AI-generated. Review for accuracy.

@deepsm007 requested in Slack thread

Summary by CodeRabbit

• Chores
  • Updated the application’s runtime environment configuration to use the current container image source.

[openshift-merge-bot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

[openshift-ci]

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

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 08a7254c-2154-4a95-bf5f-3bab8534ef54

📥 Commits

Reviewing files that changed from the base of the PR and between fd47ab2 and c459c8b.

📒 Files selected for processing (1)

• Dockerfile.ocp

---

Walkthrough

The Dockerfile runtime stage now uses the Quay-proxy OCP 5.0 CLI image.

Changes

Runtime image

Layer / File(s)	Summary
Select the runtime CLI image Dockerfile.ocp	The runtime stage changes its base image from registry.ci.openshift.org/ocp/5.0:cli to quay-proxy.ci.openshift.org/openshift/ci:ocp_5.0_cli.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the change from direct CI image references to the QCI pull-through proxy.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names	✅ Passed	The pull request changes only Dockerfile.ocp; it adds no Ginkgo tests or test titles, so the stable-name check is not applicable.
Test Structure And Quality	✅ Passed	Not applicable: the PR changes only one Dockerfile line and contains no Ginkgo declarations or Go test files to assess.
Microshift Test Compatibility	✅ Passed	The commit changes only Dockerfile.ocp and adds no Ginkgo e2e tests or OpenShift API references, so MicroShift test compatibility is not applicable.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	The commit changes only Dockerfile.ocp (one FROM reference) and adds no Ginkgo e2e tests or multi-node assumptions.
Topology-Aware Scheduling Compatibility	✅ Passed	The patch changes only Dockerfile.ocp's runtime image reference; it adds no deployment manifests, operator/controller code, or scheduling constraints.
Ote Binary Stdout Contract	✅ Passed	The PR only changes Dockerfile.ocp; the repository contains no openshift-tests binary, main function, Ginkgo suite setup, or OTE process-level stdout code.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	The PR changes only Dockerfile.ocp; it adds no Ginkgo e2e tests or test networking, IPv4 assumptions, or external connectivity requirements.
No-Weak-Crypto	✅ Passed	The commit changes only Dockerfile.ocp's image reference; scans of the added line and changed file found no weak algorithms, cipher modes, crypto APIs, or secret comparisons.
Container-Privileges	✅ Passed	The PR changes only a Dockerfile FROM reference; it adds no privileged, hostPID, hostNetwork, hostIPC, SYS_ADMIN, or allowPrivilegeEscalation setting. Existing privilege entries are unchanged.
No-Sensitive-Data-In-Logs	✅ Passed	The commit changes only the Dockerfile FROM image reference; the patch and Dockerfile contain no logging commands or sensitive-data values.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[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 ardaguclu 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

[redhat-chai-bot]

/test all

---

AI-generated. Review for accuracy.

[openshift-ci]

@redhat-chai-bot: all tests passed!

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.