Skip to content

Move from k8s.gcr.io to registry.k8s.io#109938

Merged
k8s-ci-robot merged 1 commit into
kubernetes:masterfrom
dims:move-from-k8s.gcr.io-to-registry.k8s.io
May 31, 2022
Merged

Move from k8s.gcr.io to registry.k8s.io#109938
k8s-ci-robot merged 1 commit into
kubernetes:masterfrom
dims:move-from-k8s.gcr.io-to-registry.k8s.io

Conversation

@dims

@dims dims commented May 10, 2022 •
edited by thockin
Loading

Copy link
Copy Markdown
Member

Context :

folks in sig-k8s-infra and sig-release are working towards standing up a new registry endpoint (registry.k8s.io) which enables us to store images and image signatures local to the cloud where they are being used and transparently redirect things as needed. This will help us reduce storage and transmission costs we incur in our GCR repository.

Signed-off-by: Davanum Srinivas davanum@gmail.com

What type of PR is this?

/kind feature

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

There is a new OCI image registry (registry.k8s.io) that can be used to pull kubernetes images. The old registry (k8s.gcr.io) will continue to be supported for the foreseeable future, but the new name should perform better because it frontends equivalent mirrors in other clouds.  Please point your clusters to the new registry going forward. 

Action Required: Admission/Policy integrations that have an allowlist of registries need to include "registry.k8s.io" alongside "k8s.gcr.io".
Action Required: Air-gapped environments and image garbage-collection configurations will need to update to pre-pull and preserve required images under "registry.k8s.io" as well as "k8s.gcr.io".

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:
@k8s-ci-robot k8s-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/needs-kind Indicates a PR lacks a `kind/foo` label and requires one. do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. area/apiserver area/code-generation area/conformance Issues or PRs related to kubernetes conformance tests area/kubeadm area/kubectl area/kubelet area/provider/gcp Issues or PRs related to gcp provider area/release-eng Issues or PRs related to the Release Engineering subproject area/test kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. sig/auth Categorizes an issue or PR as relevant to SIG Auth. sig/cli Categorizes an issue or PR as relevant to SIG CLI. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/release Categorizes an issue or PR as relevant to SIG Release. sig/scalability Categorizes an issue or PR as relevant to SIG Scalability. and removed do-not-merge/needs-kind Indicates a PR lacks a `kind/foo` label and requires one. do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels May 10, 2022
@nalind nalind mentioned this pull request Aug 30, 2022
Merged
This was referenced Aug 31, 2022
Merged
Merged
@lework lework mentioned this pull request Sep 2, 2022
Closed
@marquiz marquiz mentioned this pull request Sep 12, 2022
Merged
@tppolkow tppolkow mentioned this pull request Sep 20, 2022
Merged
@ameukam ameukam mentioned this pull request Oct 7, 2022
Merged
This was referenced Oct 18, 2022
Merged
Merged
@consideRatio consideRatio mentioned this pull request Oct 23, 2022
Merged
@olivierlemasle olivierlemasle mentioned this pull request Oct 24, 2022
Merged
5 tasks
@ameukam ameukam mentioned this pull request Oct 25, 2022
Closed
This was referenced Oct 27, 2022
Merged
Merged
Closed
Merged
@twz123 twz123 mentioned this pull request Nov 2, 2022
Merged
16 tasks
@olivierlemasle olivierlemasle mentioned this pull request Nov 2, 2022
Merged
This was referenced Nov 15, 2022
Merged
Merged
Merged
@jackfrancis jackfrancis mentioned this pull request Nov 18, 2022
Closed
@george-angel george-angel mentioned this pull request Nov 18, 2022
Merged
@olivierlemasle olivierlemasle mentioned this pull request Nov 28, 2022
Closed
@melalj melalj mentioned this pull request Dec 5, 2022
Closed
This was referenced Dec 7, 2022
Merged
Merged
Merged
@AndiDog AndiDog mentioned this pull request Jan 11, 2023
Closed
@outscale-mdr outscale-mdr mentioned this pull request Feb 16, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. area/apiserver area/code-generation area/conformance Issues or PRs related to kubernetes conformance tests area/kubeadm area/kubectl area/kubelet area/provider/gcp Issues or PRs related to gcp provider area/release-eng Issues or PRs related to the Release Engineering subproject area/test cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API lgtm "Looks good to me", indicates that a PR is ready to be merged. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. release-note-action-required Denotes a PR that introduces potentially breaking changes that require user action. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. sig/auth Categorizes an issue or PR as relevant to SIG Auth. sig/cli Categorizes an issue or PR as relevant to SIG CLI. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation. sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/release Categorizes an issue or PR as relevant to SIG Release. sig/scalability Categorizes an issue or PR as relevant to SIG Scalability. sig/storage Categorizes an issue or PR as relevant to SIG Storage. sig/testing Categorizes an issue or PR as relevant to SIG Testing. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. triage/accepted Indicates an issue or PR is ready to be actively worked on. wg/structured-logging Categorizes an issue or PR as relevant to WG Structured Logging.