From aaceeb69513c53b6fb861886ae86e8bf58506268 Mon Sep 17 00:00:00 2001 From: Rohit Ghumare <48523873+rohitg00@users.noreply.github.com> Date: Thu, 25 Aug 2022 13:57:27 +0530 Subject: [PATCH 1/4] Update download.md --- content/en/releases/download.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/content/en/releases/download.md b/content/en/releases/download.md index 35654994261..65e8e2d93a7 100644 --- a/content/en/releases/download.md +++ b/content/en/releases/download.md @@ -13,10 +13,10 @@ for multiple operating systems as well as hardware architectures. ## Container Images All Kubernetes container images are deployed to the -[k8s.gcr.io](https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/GLOBAL) +[registry.k8s.io](https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/GLOBAL) container registry. -{{< feature-state for_k8s_version="v1.24" state="alpha" >}} +{{< feature-state for_k8s_version="v1.25" state="alpha" >}} For Kubernetes {{< param "version" >}}, the following container images are signed using [cosign](https://github.com/sigstore/cosign) @@ -24,11 +24,11 @@ signatures: | Container Image | Supported Architectures | | ------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | -| [k8s.gcr.io/kube-apiserver:{{< param "fullversion" >}}][0] | [amd64][0-amd64], [arm][0-arm], [arm64][0-arm64], [ppc64le][0-ppc64le], [s390x][0-s390x] | -| [k8s.gcr.io/kube-controller-manager:{{< param "fullversion" >}}][1] | [amd64][1-amd64], [arm][1-arm], [arm64][1-arm64], [ppc64le][1-ppc64le], [s390x][1-s390x] | -| [k8s.gcr.io/kube-proxy:{{< param "fullversion" >}}][2] | [amd64][2-amd64], [arm][2-arm], [arm64][2-arm64], [ppc64le][2-ppc64le], [s390x][2-s390x] | -| [k8s.gcr.io/kube-scheduler:{{< param "fullversion" >}}][3] | [amd64][3-amd64], [arm][3-arm], [arm64][3-arm64], [ppc64le][3-ppc64le], [s390x][3-s390x] | -| [k8s.gcr.io/conformance:{{< param "fullversion" >}}][4] | [amd64][4-amd64], [arm][4-arm], [arm64][4-arm64], [ppc64le][4-ppc64le], [s390x][4-s390x] | +| [registry.k8s.io/kube-apiserver:{{< param "fullversion" >}}][0] | [amd64][0-amd64], [arm][0-arm], [arm64][0-arm64], [ppc64le][0-ppc64le], [s390x][0-s390x] | +| [registry.k8s.io/kube-controller-manager:{{< param "fullversion" >}}][1] | [amd64][1-amd64], [arm][1-arm], [arm64][1-arm64], [ppc64le][1-ppc64le], [s390x][1-s390x] | +| [registry.k8s.io/kube-proxy:{{< param "fullversion" >}}][2] | [amd64][2-amd64], [arm][2-arm], [arm64][2-arm64], [ppc64le][2-ppc64le], [s390x][2-s390x] | +| [registry.k8s.io/kube-scheduler:{{< param "fullversion" >}}][3] | [amd64][3-amd64], [arm][3-arm], [arm64][3-arm64], [ppc64le][3-ppc64le], [s390x][3-s390x] | +| [registry.k8s.io/conformance:{{< param "fullversion" >}}][4] | [amd64][4-amd64], [arm][4-arm], [arm64][4-arm64], [ppc64le][4-ppc64le], [s390x][4-s390x] | [0]: https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/us/kube-apiserver [0-amd64]: https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/us/kube-apiserver-amd64 @@ -65,7 +65,7 @@ All container images are available for multiple architectures, whereas the container runtime should choose the correct one based on the underlying platform. It is also possible to pull a dedicated architecture by suffixing the container image name, for example -[`k8s.gcr.io/kube-apiserver-arm64:{{< param "fullversion" >}}`][0-arm64]. All +[`registry.k8s.io/kube-apiserver-arm64:{{< param "fullversion" >}}`][0-arm64]. All those derivations are signed in the same way as the multi-architecture manifest lists. The Kubernetes project publishes a list of signed Kubernetes container images From 79d45d9915e0861593f35d1f2a11990bfa06f4ed Mon Sep 17 00:00:00 2001 From: Rohit Ghumare <48523873+rohitg00@users.noreply.github.com> Date: Thu, 25 Aug 2022 14:48:54 +0530 Subject: [PATCH 2/4] Update content/en/releases/download.md Co-authored-by: Tim Bannister --- content/en/releases/download.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/content/en/releases/download.md b/content/en/releases/download.md index 65e8e2d93a7..d5a431ff5a3 100644 --- a/content/en/releases/download.md +++ b/content/en/releases/download.md @@ -13,8 +13,7 @@ for multiple operating systems as well as hardware architectures. ## Container Images All Kubernetes container images are deployed to the -[registry.k8s.io](https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/GLOBAL) -container registry. +`registry.k8s.io` container image registry. {{< feature-state for_k8s_version="v1.25" state="alpha" >}} From 33b23906f66b4d458c7c4a880bb35508883d62f8 Mon Sep 17 00:00:00 2001 From: Rohit Ghumare <48523873+rohitg00@users.noreply.github.com> Date: Thu, 25 Aug 2022 14:49:01 +0530 Subject: [PATCH 3/4] Update content/en/releases/download.md Co-authored-by: Tim Bannister --- content/en/releases/download.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/releases/download.md b/content/en/releases/download.md index d5a431ff5a3..d82d610d4c3 100644 --- a/content/en/releases/download.md +++ b/content/en/releases/download.md @@ -15,7 +15,7 @@ for multiple operating systems as well as hardware architectures. All Kubernetes container images are deployed to the `registry.k8s.io` container image registry. -{{< feature-state for_k8s_version="v1.25" state="alpha" >}} +{{< feature-state for_k8s_version="v1.24" state="alpha" >}} For Kubernetes {{< param "version" >}}, the following container images are signed using [cosign](https://github.com/sigstore/cosign) From 9bd22c777d2ab087357561b13141648d09311442 Mon Sep 17 00:00:00 2001 From: Rohit Ghumare <48523873+rohitg00@users.noreply.github.com> Date: Thu, 25 Aug 2022 15:26:00 +0530 Subject: [PATCH 4/4] Update 2020-05-27-An-Introduction-to-the-K8s-Infrastructure-Working-Group.md default container registry change added. --- ...7-An-Introduction-to-the-K8s-Infrastructure-Working-Group.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 efd5e196f7b..58998087fad 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/wiki/New-Registry-url-for-Kubernetes-\(registry.k8s.io\)) is also fully community-owned and available for all Kubernetes subprojects to use. - 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. - There is also an automated process of promoting all our container images. This includes a fully documented infrastructure, managed by the Kubernetes community, with automated processes for provisioning permissions.