kubernetes
gcr container registry not online anymore soon
Hi all
do you have this on the radar:
https://cloud.google.com/artifact-registry/docs/transition/auto-migrate-gcr-ar?_gl=1xogfvb_gaMTE2MTE5NDI1NC4xNzQxODc0MDU5_ga_WH2QY8WWF5*MTc0MTg3NDA1OC4xLjEuMTc0MTg3NDEwOS45LjAuMA..
https://github.com/kubernetes/k8s.io/issues/3961#issuecomment-2715134242
Registries are being migrated, but mostly you don't have to worry - this is the staging repo that needs to be moved, which nobody should be using except me when cutting a release :)
@thockin , so which is the intended way (if any) to pull this without having to build it myself?
The migration is specifically for staging, which you should not use, ever. Ever ever. :)
Releases are at registry.k8s.io/git-sync/git-sync:<tag> - e.g. registry.k8s.io/git-sync/git-sync:v4.4.0
Yes, please use registry.k8s.io and do NOT use staging. We make no guarantees about staging, we might ban public read, garbage collect images, or arbitrarily move it to a different host. Staging is an internal detail of publishing images.
https://registry.k8s.io is our public image host, there are some docs there.
We are tracking staging in https://github.com/kubernetes/k8s.io/issues/3961, but again, that's project-internal. /close
@BenTheElder: Closing this issue.
In response to this:
Yes, please use registry.k8s.io and do NOT use staging. We make no guarantees about staging, we might ban public read, garbage collect images, or arbitrarily move it to a different host. Staging is an internal detail of publishing images.
https://registry.k8s.io is our public image host, there are some docs there.
We are tracking staging in https://github.com/kubernetes/k8s.io/issues/3961, but again, that's project-internal. /close
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 kubernetes-sigs/prow repository.
