chore: replace k8s.gcr.io registry usage #6040
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
shaneutt
force-pushed
the
shaneutt/replace-gcr.io-registry
branch
from
202c5aa to
45a06aa
Compare
shaneutt
changed the title
shaneutt
force-pushed
the
shaneutt/replace-gcr.io-registry
branch
from
45a06aa to
477625a
Compare
shaneutt
requested review from
a team,
lobkovilya and
lukidzi
and removed request for
a team
Signed-off-by: Shane Utt <[email protected]>
bartsmykla
approved these changes
Feb 15, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Kubernetes is replacing the k8s.gcr.io registry. Besides it just becoming frozen soon the new registry.k8s.io registry is also less costly to use so the sooner we can stop using the old one the better to help out upstream.