OSAC-1534: Replace docker.io/envoyproxy/envoy with ghcr.io mirror

[eliorerz]

Summary

• Replace all docker.io/envoyproxy/envoy image references with ghcr.io/osac-project/envoy to avoid Docker Hub rate limits and ImagePullBackOff on disconnected clusters
• Add a GitHub Actions workflow (.github/workflows/mirror-envoy.yaml) to mirror the envoy image from Docker Hub to GHCR, triggered manually or on a weekly schedule

Files changed

File	Change
.github/workflows/mirror-envoy.yaml	New — image mirroring workflow
base/kustomization.yaml	Update envoy newName
charts/osac/values.yaml	Update envoy image
charts/osac/values-example.yaml	Update envoy image
values/development.yaml	Update envoy image
values/vmaas-ci.yaml	Update envoy image
values/caas-ci.yaml	Update envoy image

Pre-requisites

1. Mirror the image: After merging, run the Mirror Envoy Image workflow manually with v1.33.0 to push the image to GHCR. Otherwise deployed clusters will get ImagePullNotFound.
2. Set package visibility to public: The ghcr.io/osac-project/envoy package will be created as private by default. It must be changed to public in the osac-project org package settings after the first push, otherwise clusters without GHCR auth will still get ImagePullBackOff.

Test plan

• Run mirror-envoy workflow manually with v1.33.0 and verify ghcr.io/osac-project/envoy:v1.33.0 exists
• Set ghcr.io/osac-project/envoy package visibility to public
• helm lint charts/osac/ passes
• helm template with all CI values files succeeds and shows ghcr.io/osac-project/envoy:v1.33.0
• No docker.io/envoyproxy references remain outside submodules and the mirror workflow SOURCE
• kustomize build base/ produces no docker.io/envoyproxy references

[openshift-ci-robot]

@eliorerz: This pull request references OSAC-1534 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 task to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Summary

• Replace all docker.io/envoyproxy/envoy image references with ghcr.io/osac-project/envoy to avoid Docker Hub rate limits and ImagePullBackOff on disconnected clusters
• Add a GitHub Actions workflow (.github/workflows/mirror-envoy.yaml) to mirror the envoy image from Docker Hub to GHCR, triggered manually or on a weekly schedule

Files changed

File	Change
.github/workflows/mirror-envoy.yaml	New — image mirroring workflow
base/kustomization.yaml	Update envoy newName
charts/osac/values.yaml	Update envoy image
charts/osac/values-example.yaml	Update envoy image
values/development.yaml	Update envoy image
values/vmaas-ci.yaml	Update envoy image
values/caas-ci.yaml	Update envoy image

Pre-requisite

Before merging, the mirror workflow must be run manually with v1.33.0 to push the image to GHCR. Otherwise deployed clusters will get ImagePullNotFound.

Test plan

• Run mirror-envoy workflow manually with v1.33.0 and verify ghcr.io/osac-project/envoy:v1.33.0 exists
• helm lint charts/osac/ passes
• helm template with all CI values files succeeds and shows ghcr.io/osac-project/envoy:v1.33.0
• No docker.io/envoyproxy references remain outside submodules and the mirror workflow SOURCE
• kustomize build base/ produces no docker.io/envoyproxy references

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 APPROVED

This pull-request has been approved by: eliorerz

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [eliorerz]

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

[coderabbitai]

Warning

Review limit reached

@eliorerz, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 34 minutes and 6 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository: osac-project/coderabbit/.coderabbit.yaml

Review profile: ASSERTIVE

Plan: Enterprise

Run ID: 9e3fe32c-7d60-4473-abef-a573b26cd31f

📥 Commits

Reviewing files that changed from the base of the PR and between 4f1b57e and 21d3151.

📒 Files selected for processing (7)

• .github/workflows/mirror-envoy.yaml
• base/kustomization.yaml
• charts/osac/values-example.yaml
• charts/osac/values.yaml
• values/caas-ci.yaml
• values/development.yaml
• values/vmaas-ci.yaml

✨ 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 and usage tips.}