From ec4fe4b64e79d7826f98aae8ad6d54ac90545609 Mon Sep 17 00:00:00 2001 From: Sergey Kanzhelev Date: Sat, 28 Jan 2023 05:26:32 -0800 Subject: [PATCH] registry change in docs (k8s.gcr.io -> registry.k8s.io) (#38501) * registry change in en docs * Update content/en/blog/_posts/2019-04-04-local-persistent-volumes-ga.md Co-authored-by: Tim Bannister * Update content/en/blog/_posts/2019-04-04-local-persistent-volumes-ga.md Co-authored-by: Tim Bannister * Update content/en/blog/_posts/2022-05-13-grpc-probes-in-beta.md Co-authored-by: Tim Bannister * Update content/en/blog/_posts/2022-05-27-maxunavailable-for-statefulset.md Co-authored-by: Tim Bannister --------- Co-authored-by: Tim Bannister --- .../en/blog/_posts/2019-04-04-local-persistent-volumes-ga.md | 2 +- ...n-Introduction-to-the-K8s-Infrastructure-Working-Group.md | 2 +- content/en/blog/_posts/2022-05-13-grpc-probes-in-beta.md | 3 ++- .../blog/_posts/2022-05-27-maxunavailable-for-statefulset.md | 5 +++-- 4 files changed, 7 insertions(+), 5 deletions(-) diff --git a/content/en/blog/_posts/2019-04-04-local-persistent-volumes-ga.md b/content/en/blog/_posts/2019-04-04-local-persistent-volumes-ga.md index c3681bd1d68da..61a37e3f123e0 100644 --- a/content/en/blog/_posts/2019-04-04-local-persistent-volumes-ga.md +++ b/content/en/blog/_posts/2019-04-04-local-persistent-volumes-ga.md @@ -129,7 +129,7 @@ spec: spec: containers: - name: test-container - image: k8s.gcr.io/busybox + image: registry.k8s.io/busybox # updated after publication (previously used k8s.gcr.io/busybox) command: - "/bin/sh" args: diff --git a/content/en/blog/_posts/2020-05-27-An-Introduction-to-the-K8s-Infrastructure-Working-Group.md b/content/en/blog/_posts/2020-05-27-An-Introduction-to-the-K8s-Infrastructure-Working-Group.md index f16fad7105d98..3bab474a4b70b 100644 --- a/content/en/blog/_posts/2020-05-27-An-Introduction-to-the-K8s-Infrastructure-Working-Group.md +++ b/content/en/blog/_posts/2020-05-27-An-Introduction-to-the-K8s-Infrastructure-Working-Group.md @@ -55,7 +55,7 @@ The team has made progress in the last few months that is well worth celebrating - The K8s-Infrastructure Working Group released an automated billing report that they start every meeting off by reviewing as a group. - DNS for k8s.io and kubernetes.io are also fully [community-owned](https://groups.google.com/g/kubernetes-dev/c/LZTYJorGh7c/m/u-ydk-yNEgAJ), with community members able to [file issues](https://github.com/kubernetes/k8s.io/issues/new?assignees=&labels=wg%2Fk8s-infra&template=dns-request.md&title=DNS+REQUEST%3A+%3Cyour-dns-record%3E) to manage records. -- The container registry [k8s.gcr.io](https://github.com/kubernetes/k8s.io/tree/main/k8s.gcr.io) is also fully community-owned and available for all Kubernetes subprojects to use. +- The container registry [registry.k8s.io](https://github.com/kubernetes/k8s.io/tree/main/registry.k8s.io) is also fully community-owned and available for all Kubernetes subprojects to use. _Note:_ The container registry has changed to registry.k8s.io. Updated on August 25, 2022. - The Kubernetes [publishing-bot](https://github.com/kubernetes/publishing-bot) responsible for keeping k8s.io/kubernetes/staging repositories published to their own top-level repos (For example: [kubernetes/api](https://github.com/kubernetes/api)) runs on a community-owned cluster. - The gcsweb.k8s.io service used to provide anonymous access to GCS buckets for kubernetes artifacts runs on a community-owned cluster. diff --git a/content/en/blog/_posts/2022-05-13-grpc-probes-in-beta.md b/content/en/blog/_posts/2022-05-13-grpc-probes-in-beta.md index 619f82e021b8f..e4a9ab0092cb3 100644 --- a/content/en/blog/_posts/2022-05-13-grpc-probes-in-beta.md +++ b/content/en/blog/_posts/2022-05-13-grpc-probes-in-beta.md @@ -115,7 +115,8 @@ metadata: spec: containers: - name: agnhost - image: k8s.gcr.io/e2e-test-images/agnhost:2.35 + # image changed since publication (previously used registry "k8s.gcr.io") + image: registry.k8s.io/e2e-test-images/agnhost:2.35 command: ["/agnhost", "grpc-health-checking"] ports: - containerPort: 5000 diff --git a/content/en/blog/_posts/2022-05-27-maxunavailable-for-statefulset.md b/content/en/blog/_posts/2022-05-27-maxunavailable-for-statefulset.md index 5dd786d9ad741..5d34a7196cdec 100644 --- a/content/en/blog/_posts/2022-05-27-maxunavailable-for-statefulset.md +++ b/content/en/blog/_posts/2022-05-27-maxunavailable-for-statefulset.md @@ -50,7 +50,8 @@ spec: app: nginx spec: containers: - - image: k8s.gcr.io/nginx-slim:0.8 + # image changed since publication (previously used registry "k8s.gcr.io") + - image: registry.k8s.io/nginx-slim:0.8 imagePullPolicy: IfNotPresent name: nginx updateStrategy: @@ -66,7 +67,7 @@ If you enable the new feature and you don't specify a value for `maxUnavailable` I'll run through a scenario based on that example manifest to demonstrate how this feature works. I will deploy a StatefulSet that has 5 replicas, with `maxUnavailable` set to 2 and `partition` set to 0. -I can trigger a rolling update by changing the image to `k8s.gcr.io/nginx-slim:0.9`. Once I initiate the rolling update, I can +I can trigger a rolling update by changing the image to `registry.k8s.io/nginx-slim:0.9`. Once I initiate the rolling update, I can watch the pods update 2 at a time as the current value of maxUnavailable is 2. The below output shows a span of time and is not complete. The maxUnavailable can be an absolute number (for example, 2) or a percentage of desired Pods (for example, 10%). The absolute number is calculated from percentage by rounding up to the nearest integer.