-
Notifications
You must be signed in to change notification settings - Fork 519
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
Removes k8s.gcr.io in favor of registry.k8s.io #2786
Conversation
Drafting this to address this setting needing a migration |
a3c4845
to
4249a09
Compare
Force pushed to add migration for the Testing incoming!! |
4249a09
to
bb74b8a
Compare
Force pushed to add missing update to |
- Adds migration for settings.kubernetes.pod-infra-container-image Signed-off-by: John McBride <[email protected]>
bb74b8a
to
3623d42
Compare
Force pushed to import correct migration helper. Ok! Now testing should be incoming soon!! |
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.
🎉
Ran migrations tests for vmware variant with custom built tuf repo and
👍🏼 |
Issue number:
N/a -
k8s.gcr.io
is being deprecated in favor ofregistry.k8s.io
.See: https://kubernetes.io/blog/2023/02/06/k8s-gcr-io-freeze-announcement/
Description of changes:
Replaces registry for pause image. Image is present:
Testing done:
What testing should we do here since this only affects defaults for vmware k8s?
Terms of contribution:
By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.