-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🌱 Use new registry in published manifests #7410
Conversation
Skipping CI for Draft Pull Request. |
/test all |
This needs some time for review, I will try to make a first pass before KubeCon |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tl;dr there are a few places where we have to keep the old registry.
We will only migrate from the old to the new registry after certain Kubernetes releases, which is why we can't just replace all occurences of the old registry with the new one
Basically the only behavioral change we want is the one in the Makefile (some of the changes like unit / e2e tests / doc are fine though)
test/framework/kubernetesversions/data/debian_injection_script.envsubst.sh.tpl
Outdated
Show resolved
Hide resolved
Thank you very much!! /lgtm Trying this out with the beta release today |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbueringer The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retitle 🌱 Use new registry in published manifests |
@sbueringer Thank you for your great help and encouragement 🙏 |
You're welcome :). Thx for working on this issue :) |
What this PR does / why we need it:
This pr replaces all
k8s.gcr.io
withregistry.k8s.io
. I remember trying this a while back and running into issues due to some images not being available. But now it seems to work for the none malformed image registries.Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #7402