Merge pull request #36532 from Michelle951/michelle00

[zh] sync content/zh-cn/releases/download.md
This commit is contained in:
Kubernetes Prow Robot 2022-09-03 17:58:35 -07:00 committed by GitHub
commit 001eeb266c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 11 additions and 12 deletions

View File

@ -24,13 +24,12 @@ Kubernetes 为每个组件提供二进制文件以及一组标准的客户端应
## Container Images ## Container Images
All Kubernetes container images are deployed to the 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` container image registry.
container registry.
--> -->
## 容器镜像 ## 容器镜像
所有 Kubernetes 容器镜像都部署到 所有 Kubernetes 容器镜像都部署到
[k8s.gcr.io](https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/GLOBAL) 容器仓库。 `registry.k8s.io` 容器镜像仓库。
{{< feature-state for_k8s_version="v1.24" state="alpha" >}} {{< feature-state for_k8s_version="v1.24" state="alpha" >}}
@ -48,11 +47,11 @@ signatures:
--> -->
| 容器镜像 | 支持架构 | | 容器镜像 | 支持架构 |
| ------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | | ------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
| [k8s.gcr.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-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] | | [registry.k8s.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] | | [registry.k8s.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] | | [registry.k8s.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/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]: 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 [0-amd64]: https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/us/kube-apiserver-amd64
@ -90,12 +89,12 @@ All container images are available for multiple architectures, whereas the
container runtime should choose the correct one based on the underlying container runtime should choose the correct one based on the underlying
platform. It is also possible to pull a dedicated architecture by suffixing the platform. It is also possible to pull a dedicated architecture by suffixing the
container image name, for example 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. those derivations are signed in the same way as the multi-architecture manifest lists.
--> -->
所有容器镜像都支持多种体系结构,容器运行时应根据下层平台选择正确的镜像。 所有容器镜像都支持多构,容器运行时应根据下层平台选择正确的镜像。
也可以通过给容器镜像名称加后缀来拉取特定体系结构的镜像,例如 也可以通过给容器镜像名称加后缀来拉取适合特定架构的镜像,例如
[`k8s.gcr.io/kube-apiserver-arm64:{{< param "fullversion" >}}`][0-arm64]。 [`registry.k8s.io/kube-apiserver-arm64:{{< param "fullversion" >}}`][0-arm64]。
所有这些派生镜像都以与多架构清单列表相同的方式签名。 所有这些派生镜像都以与多架构清单列表相同的方式签名。
<!-- <!--