Skip to content
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

Migrate from k8s.gcr.io to registry.k8s.io #2021

Conversation

aniruddha2000
Copy link

This PR migrate from k8s.gcr.io to registry.k8s.io

Part Of kubernetes/k8s.io#4780

Signed-off-by: Aniruddha Basak <codewithaniruddha@gmail.com>
@@ -375,7 +375,7 @@ After update, the following will be written to your Docker config file located a
"us.gcr.io": "gcloud",
"eu.gcr.io": "gcloud",
"asia.gcr.io": "gcloud",
"staging-k8s.gcr.io": "gcloud",
"staging-registry.k8s.io": "gcloud",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

$ nslookup staging-registry.k8s.io
;; connection timed out; no servers could be reached

@AkihiroSuda
Copy link
Member

gcloud (418.0.0) seems still using staging-k8s.gcr.io

@mrbobbytables
Copy link

Just an FYI - staging-k8s.gcr.io used to be a push only endpoint, however that is no longer the case and largely acts as a placeholder to swap out for other addresses. It should be safe to remove, but also fine to leave as is. It won't really be used for anything.

This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants