|
| 1 | +--- |
| 2 | +title: 下载 Kubernetes |
| 3 | +type: docs |
| 4 | +--- |
| 5 | +<!-- |
| 6 | +title: Download Kubernetes |
| 7 | +type: docs |
| 8 | +--> |
| 9 | + |
| 10 | +<!-- |
| 11 | +Kubernetes ships binaries for each component as well as a standard set of client |
| 12 | +applications to bootstrap or interact with a cluster. Components like the |
| 13 | +API server are capable of running within container images inside of a |
| 14 | +cluster. Those components are also shipped in container images as part of the |
| 15 | +official release process. All binaries as well as container images are available |
| 16 | +for multiple operating systems as well as hardware architectures. |
| 17 | +--> |
| 18 | +Kubernetes 为每个组件提供二进制文件以及一组标准的客户端应用程序用来引导集群或与集群交互。 |
| 19 | +像 API 服务器这样的组件能够在集群内的容器镜像中运行。 |
| 20 | +作为官方发布过程的一部分,这些组件也以容器镜像的形式提供。 |
| 21 | +所有二进制文件和容器镜像都可用于多种操作系统和硬件架构。 |
| 22 | + |
| 23 | +<!-- |
| 24 | +## Container Images |
| 25 | +
|
| 26 | +All Kubernetes container images are deployed to the |
| 27 | +[k8s.gcr.io](https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/GLOBAL) |
| 28 | +container registry. |
| 29 | +--> |
| 30 | +## 容器镜像 |
| 31 | + |
| 32 | +所有 Kubernetes 容器镜像都部署到 |
| 33 | +[k8s.gcr.io](https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/GLOBAL) 容器仓库。 |
| 34 | + |
| 35 | + |
| 36 | +{{< feature-state for_k8s_version="v1.24" state="alpha" >}} |
| 37 | + |
| 38 | +<!-- |
| 39 | +For Kubernetes {{< param "version" >}}, the following |
| 40 | +container images are signed using [cosign](https://github.com/sigstore/cosign) |
| 41 | +signatures: |
| 42 | +--> |
| 43 | +对于 Kubernetes {{< param "version" >}},以下容器镜像使用 |
| 44 | +[cosign](https://github.com/sigstore/cosign) 进行签名: |
| 45 | + |
| 46 | +<!-- |
| 47 | +| Container Image | Supported Architectures | |
| 48 | +--> |
| 49 | +| 容器镜像 | 支持架构 | |
| 50 | +| ------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | |
| 51 | +| [k8s.gcr.io/kube-apiserver:{{< param "fullversion" >}}][0] | [amd64][0-amd64], [arm][0-arm], [arm64][0-arm64], [ppc64le][0-ppc64le], [s390x][0-s390x] | |
| 52 | +| [k8s.gcr.io/kube-controller-manager:{{< param "fullversion" >}}][1] | [amd64][1-amd64], [arm][1-arm], [arm64][1-arm64], [ppc64le][1-ppc64le], [s390x][1-s390x] | |
| 53 | +| [k8s.gcr.io/kube-proxy:{{< param "fullversion" >}}][2] | [amd64][2-amd64], [arm][2-arm], [arm64][2-arm64], [ppc64le][2-ppc64le], [s390x][2-s390x] | |
| 54 | +| [k8s.gcr.io/kube-scheduler:{{< param "fullversion" >}}][3] | [amd64][3-amd64], [arm][3-arm], [arm64][3-arm64], [ppc64le][3-ppc64le], [s390x][3-s390x] | |
| 55 | +| [k8s.gcr.io/conformance:{{< param "fullversion" >}}][4] | [amd64][4-amd64], [arm][4-arm], [arm64][4-arm64], [ppc64le][4-ppc64le], [s390x][4-s390x] | |
| 56 | + |
| 57 | +[0]: https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/us/kube-apiserver |
| 58 | +[0-amd64]: https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/us/kube-apiserver-amd64 |
| 59 | +[0-arm]: https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/us/kube-apiserver-arm |
| 60 | +[0-arm64]: https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/us/kube-apiserver-arm64 |
| 61 | +[0-ppc64le]: https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/us/kube-apiserver-ppc64le |
| 62 | +[0-s390x]: https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/us/kube-apiserver-s390x |
| 63 | +[1]: https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/us/kube-controller-manager |
| 64 | +[1-amd64]: https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/us/kube-controller-manager-amd64 |
| 65 | +[1-arm]: https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/us/kube-controller-manager-arm |
| 66 | +[1-arm64]: https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/us/kube-controller-manager-arm64 |
| 67 | +[1-ppc64le]: https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/us/kube-controller-manager-ppc64le |
| 68 | +[1-s390x]: https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/us/kube-controller-manager-s390x |
| 69 | +[2]: https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/us/kube-proxy |
| 70 | +[2-amd64]: https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/us/kube-proxy-amd64 |
| 71 | +[2-arm]: https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/us/kube-proxy-arm |
| 72 | +[2-arm64]: https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/us/kube-proxy-arm64 |
| 73 | +[2-ppc64le]: https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/us/kube-proxy-ppc64le |
| 74 | +[2-s390x]: https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/us/kube-proxy-s390x |
| 75 | +[3]: https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/us/kube-scheduler |
| 76 | +[3-amd64]: https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/us/kube-scheduler-amd64 |
| 77 | +[3-arm]: https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/us/kube-scheduler-arm |
| 78 | +[3-arm64]: https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/us/kube-scheduler-arm64 |
| 79 | +[3-ppc64le]: https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/us/kube-scheduler-ppc64le |
| 80 | +[3-s390x]: https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/us/kube-scheduler-s390x |
| 81 | +[4]: https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/us/conformance |
| 82 | +[4-amd64]: https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/us/conformance-amd64 |
| 83 | +[4-arm]: https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/us/conformance-arm |
| 84 | +[4-arm64]: https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/us/conformance-arm64 |
| 85 | +[4-ppc64le]: https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/us/conformance-ppc64le |
| 86 | +[4-s390x]: https://console.cloud.google.com/gcr/images/k8s-artifacts-prod/us/conformance-s390x |
| 87 | + |
| 88 | +<!-- |
| 89 | +All container images are available for multiple architectures, whereas the |
| 90 | +container runtime should choose the correct one based on the underlying |
| 91 | +platform. It is also possible to pull a dedicated architecture by suffixing the |
| 92 | +container image name, for example |
| 93 | +[`k8s.gcr.io/kube-apiserver-arm64:{{< param "fullversion" >}}`][0-arm64]. All |
| 94 | +those derivations are signed in the same way as the multi-architecture manifest lists. |
| 95 | +--> |
| 96 | +所有容器镜像都支持多种体系结构,容器运行时应根据下层平台选择正确的镜像。 |
| 97 | +也可以通过给容器镜像名称加后缀来拉取特定体系结构的镜像,例如 |
| 98 | +[`k8s.gcr.io/kube-apiserver-arm64:{{< param "fullversion" >}}`][0-arm64]。 |
| 99 | +所有这些派生镜像都以与多架构清单列表相同的方式签名。 |
| 100 | + |
| 101 | +<!-- |
| 102 | +The Kubernetes project publishes a list of signed Kubernetes container images |
| 103 | +in SBoM (Software Bill of Materials) format. |
| 104 | +You can fetch that list using: |
| 105 | +--> |
| 106 | +Kubernetes 项目以 SBoM(软件物料清单)格式发布已签名的 Kubernetes 容器镜像列表。 |
| 107 | +你可以使用以下方法获取该列表: |
| 108 | + |
| 109 | +```shell |
| 110 | +curl -Ls "https://sbom.k8s.io/$(curl -Ls https://dl.k8s.io/release/latest.txt)/release" | awk '/PackageName: k8s.gcr.io\// {print $2}' |
| 111 | +``` |
| 112 | +<!-- |
| 113 | +For Kubernetes v{{< skew currentVersion >}}, the only kind of code artifact that |
| 114 | +you can verify integrity for is a container image, using the experimental |
| 115 | +signing support. |
| 116 | +
|
| 117 | +To manually verify signed container images of Kubernetes core components, refer to |
| 118 | +[Verify Signed Container Images](/docs/tasks/administer-cluster/verify-signed-images). |
| 119 | +--> |
| 120 | +对于 Kubernetes v{{< skew currentVersion >}},唯一可以验证完整性的代码工件就是容器镜像,它使用实验性签名支持。 |
| 121 | + |
| 122 | +如需手动验证 Kubernetes 核心组件的签名容器镜像,请参考[验证签名容器镜像](/zh/docs/tasks/administer-cluster/verify-signed-images)。 |
| 123 | + |
| 124 | +<!-- |
| 125 | +## Binaries |
| 126 | +
|
| 127 | +Find links to download Kubernetes components (and their checksums) in the [CHANGELOG](https://github.com/kubernetes/kubernetes/tree/master/CHANGELOG) files. |
| 128 | +
|
| 129 | +Alternately, use [downloadkubernetes.com](https://www.downloadkubernetes.com/) to filter by version and architecture. |
| 130 | +--> |
| 131 | +## 二进制 |
| 132 | + |
| 133 | +在 [CHANGELOG](https://github.com/kubernetes/kubernetes/tree/master/CHANGELOG) 文件中找到下载 Kubernetes 组件(及其校验和)的链接。 |
| 134 | + |
| 135 | +或者,使用 [downloadkubernetes.com](https://www.downloadkubernetes.com/) 按版本和架构进行过滤。 |
| 136 | + |
| 137 | +### kubectl |
| 138 | + |
| 139 | +<!-- overview --> |
| 140 | + |
| 141 | +<!-- |
| 142 | +The Kubernetes command-line tool, [kubectl](/docs/reference/kubectl/kubectl/), allows |
| 143 | +you to run commands against Kubernetes clusters. |
| 144 | +
|
| 145 | +You can use kubectl to deploy applications, inspect and manage cluster resources, |
| 146 | +and view logs. For more information including a complete list of kubectl operations, see the |
| 147 | +[`kubectl` reference documentation](/docs/reference/kubectl/). |
| 148 | +--> |
| 149 | +Kubernetes 命令行工具 [kubectl](/zh/docs/reference/kubectl/kubectl/) 允许你对 Kubernetes 集群执行命令。 |
| 150 | + |
| 151 | +你可以使用 kubectl 部署应用程序、检查和管理集群资源以及查看日志。 |
| 152 | +有关更多信息,包括 kubectl 操作的完整列表,请参阅 |
| 153 | +[`kubectl` 参考文档](/zh/docs/reference/kubectl/)。 |
| 154 | + |
| 155 | +<!-- |
| 156 | +kubectl is installable on a variety of Linux platforms, macOS and Windows. |
| 157 | +Find your preferred operating system below. |
| 158 | +
|
| 159 | +- [Install kubectl on Linux](/docs/tasks/tools/install-kubectl-linux) |
| 160 | +- [Install kubectl on macOS](/docs/tasks/tools/install-kubectl-macos) |
| 161 | +- [Install kubectl on Windows](/docs/tasks/tools/install-kubectl-windows) |
| 162 | +--> |
| 163 | +kubectl 可安装在各种 Linux 平台、macOS 和 Windows 上。 |
| 164 | +在下方找到你首选的操作系统。 |
| 165 | + |
| 166 | +- [在 Linux 上安装 kubectl](/zh/docs/tasks/tools/install-kubectl-linux) |
| 167 | +- [在 macOS 上安装 kubectl](/zh/docs/tasks/tools/install-kubectl-macos) |
| 168 | +- [在 Windows 上安装 kubectl](/zh/docs/tasks/tools/install-kubectl-windows) |
0 commit comments