-
Notifications
You must be signed in to change notification settings - Fork 13.8k
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
Replace deprecated k8s registry references #29938
Replace deprecated k8s registry references #29938
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Its impossible to set both 2.5.2 and helm chart milestone in a single PR :)
2.5.2 is much more important to our workflow than the helm chart, so let's mark it for that one. |
@eladkal I can move the helm changes to a new PR if it's preferred. WDYT? |
That is up to @jedcunningham @ephraimbuddy as release managers for core and helm chart. If they don't mind than it's OK :) |
Also - generally speaking helm chart is released from main - so once this one is merged, the next helm chart release will contain it. No need to put it to milestone. |
(cherry picked from commit e0fadf9)
k8s.gcr.io
image registry will be frozen from the 3rd of April 2023 according to this announcement, and it was replaced byregistry.k8s.io
which contains already all the images.