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
Move from k8s.gcr.io to registry.k8s.io #109938
Merged
k8s-ci-robot
merged 1 commit into
kubernetes:master
from
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:master
from
dims:move-from-k8s.gcr.io-to-registry.k8s.io
May 31, 2022
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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
zshi-redhat
added a commit
to zshi-redhat/microshift
that referenced
this pull request
Oct 21, 2022
Kubernetes moved from k8s.gcr.io to registry.k8s.io in 1.15 via: kubernetes/kubernetes#109938 With old k8s.grc.io, pods failed to start in offline mode since it cannot resolve registry.k8s.io or download the new pause image: Warning FailedCreatePodSandBox 10s (x7 over 92s) kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = error creating pod sandbox with name "k8s_ovnkube-master-84dtp_openshift-ovn-kubernetes_cb245daf-ef1d-4610-9f9b-77f7d0af8dc7_0": initializing source docker://registry.k8s.io/pause:3.6: pinging container registry registry.k8s.io: Get "https://registry.k8s.io/v2/": dial tcp: lookup registry.k8s.io on 192.168.100.1:53: server misbehaving
olivierlemasle
added a commit
to olivierlemasle/kube-prometheus
that referenced
this pull request
Oct 24, 2022
Kubernetes has switched registry from k8s.gcr.io to registry.k8s.io in kubernetes/kubernetes#109938. kube-state-metrics also did the switch in kubernetes/kube-state-metrics#1750. This commit also updates the registry in a kubeadm configuration example.
5 tasks
mangelajo
pushed a commit
to openshift/microshift
that referenced
this pull request
Oct 25, 2022
Kubernetes moved from k8s.gcr.io to registry.k8s.io in 1.15 via: kubernetes/kubernetes#109938 With old k8s.grc.io, pods failed to start in offline mode since it cannot resolve registry.k8s.io or download the new pause image: Warning FailedCreatePodSandBox 10s (x7 over 92s) kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = error creating pod sandbox with name "k8s_ovnkube-master-84dtp_openshift-ovn-kubernetes_cb245daf-ef1d-4610-9f9b-77f7d0af8dc7_0": initializing source docker://registry.k8s.io/pause:3.6: pinging container registry registry.k8s.io: Get "https://registry.k8s.io/v2/": dial tcp: lookup registry.k8s.io on 192.168.100.1:53: server misbehaving
This was referenced Oct 27, 2022
16 tasks
olivierlemasle
added a commit
to olivierlemasle/cluster-monitoring-operator
that referenced
this pull request
Nov 2, 2022
Kubernetes has switched registry from k8s.gcr.io to registry.k8s.io in kubernetes/kubernetes#109938. kube-state-metrics also did the switch in kubernetes/kube-state-metrics#1750. Signed-off-by: Olivier Lemasle <olivier.lemasle@apalia.net>
philipgough
pushed a commit
to prometheus-operator/kube-prometheus
that referenced
this pull request
Nov 7, 2022
Kubernetes has switched registry from k8s.gcr.io to registry.k8s.io in kubernetes/kubernetes#109938. kube-state-metrics also did the switch in kubernetes/kube-state-metrics#1750. This commit also updates the registry in a kubeadm configuration example.
This was referenced Nov 15, 2022
george-angel
added a commit
to utilitywarehouse/tf_kube_ignition
that referenced
this pull request
Nov 18, 2022
george-angel
added a commit
to utilitywarehouse/grafana-manifests
that referenced
this pull request
Nov 18, 2022
george-angel
added a commit
to utilitywarehouse/terraform-applier
that referenced
this pull request
Nov 18, 2022
This was referenced Dec 7, 2022
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.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: