Repoint registry from k8s.gcr.io to registry.k8s.io as legacy one will be frozen soon #1197
Assignees
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Comments
k8s-ci-robot
added
kind/feature
|
Looks like this change was implemented in 2155c29 - but the latest version of the chart doesn't have this particular change - presumable just cutting a new release should include that change |
|
/triage accepted |
k8s-ci-robot
added
triage/accepted
|
The images are already published to the new registry so this won't be a problem. I'll cut v0.6.3 soon with new manifests pointing to the new registry. We will most likely release a new helm chart after that. |
|
You can track the progress of the new release in #1203. |
|
Closing since the change is now available in release v0.6.3 https://github.com/kubernetes-sigs/metrics-server/releases/tag/v0.6.3. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What would you like to be updated:
Update the registry from
k8s.gcr.iotoregistry.k8s.iofor container image.At the moment it does resolve to
k8s.gcr.io/metrics-server/metrics-server:v0.6.2.Why is this needed:
The legacy registry will be frozen from 3rd of April 2023.
Mode context here https://kubernetes.io/blog/2023/02/06/k8s-gcr-io-freeze-announcement/
/kind feature
The text was updated successfully, but these errors were encountered: