Skip to content
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

[Action Required] Update references from k8s.gcr.io to registry.k8s.io #5491

Closed
mrbobbytables opened this issue Feb 9, 2023 · 2 comments · Fixed by #5494
Closed

[Action Required] Update references from k8s.gcr.io to registry.k8s.io #5491

mrbobbytables opened this issue Feb 9, 2023 · 2 comments · Fixed by #5494
Assignees
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/autoscaling Categorizes an issue or PR as relevant to SIG Autoscaling.

Comments

@mrbobbytables
Copy link
Member

With the change to defaulting to registry.k8s.io as our image registry and the planned freeze in April, projects within the Kubernetes orgs should update their image references to point to the new address.

NOTE: We can ignore references to staging-k8s.gcr.io, but any other references to k8s.gcr.io should be updated to registry.k8s.io

k8s.gcr.io search results

ref: [Umbrella Issue] Migrate K8s projects from k8s.gcr.io -> registry.k8s.io

(similar issue: #5486)

/kind cleanup
/sig autoscaling
/priority important-soon

@k8s-ci-robot k8s-ci-robot added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. sig/autoscaling Categorizes an issue or PR as relevant to SIG Autoscaling. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Feb 9, 2023
@mrbobbytables mrbobbytables changed the title Update references from k8s.gcr.io to registry.k8s.io [Action Required] Update references from k8s.gcr.io to registry.k8s.io Feb 9, 2023
@gjtempleton gjtempleton added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Feb 9, 2023
@salasberryfin
Copy link
Contributor

I saw this labeled as good first issue in other projects, can I pick this up?

/assign

@jbartosik
Copy link
Collaborator

For VPA we build & push images to gcr.io/k8s-staging-autoscaling(see RELEASE.md), then automation pushes those images to k8s.gcr.io/autoscaling after we apply changes to images.yaml (see RELEASE.md).

Addon resizer has similar release process (not documented in the repo). Looking at the images.yaml I think Cluster Autoscaler has similar release process too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/autoscaling Categorizes an issue or PR as relevant to SIG Autoscaling.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants