You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"On the 3rd of April 2023, the old registry k8s.gcr.io will be frozen and no further images for Kubernetes and related subprojects will be pushed to the old registry.
This registry registry.k8s.io replaced the old one and has been generally available for several months. We have published a blog post about its benefits to the community and the Kubernetes project."
xing-yang
added
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
and removed
kind/bug
Categorizes issue or PR as related to a bug.
labels
Feb 16, 2023
"On the 3rd of April 2023, the old registry k8s.gcr.io will be frozen and no further images for Kubernetes and related subprojects will be pushed to the old registry.
This registry registry.k8s.io replaced the old one and has been generally available for several months. We have published a blog post about its benefits to the community and the Kubernetes project."
The full email notification is here: https://groups.google.com/a/kubernetes.io/g/dev/c/Oq8HUQJQkXQ
https://cs.k8s.io/?q=k8s.gcr.io&i=nope&files=&excludeFiles=vendor%2F&repos=kubernetes-sigs/vsphere-csi-driver
Is this a BUG REPORT or FEATURE REQUEST?:
/kind cleanup
What happened:
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
uname -a
):The text was updated successfully, but these errors were encountered: