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
Starting next Monday redirects will happen automatically to registry.k8s.io. While this is designed to make the switch more transparent and give people more time to migrate, it might not be without impact to your build or execution environment. For more background, see here: https://kubernetes.io/blog/2023/03/10/image-registry-redirect/
👉 Call to action: if you are using images from k8s.gcr.io in any of your build dependencies or runtime dependencies, you should update the image references to registry.k8s.io as soon as possible.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi all,
some of you may have heard this already, but the official image registry for the Kubernetes community is changing from
k8s.gcr.io
toregistry.k8s.io
, for background see here: https://kubernetes.io/blog/2022/11/28/registry-k8s-io-faster-cheaper-ga/Starting next Monday redirects will happen automatically to
registry.k8s.io
. While this is designed to make the switch more transparent and give people more time to migrate, it might not be without impact to your build or execution environment. For more background, see here: https://kubernetes.io/blog/2023/03/10/image-registry-redirect/👉 Call to action: if you are using images from
k8s.gcr.io
in any of your build dependencies or runtime dependencies, you should update the image references toregistry.k8s.io
as soon as possible.Beta Was this translation helpful? Give feedback.
All reactions