website/content/zh-cn/releases/download.md

---
title: 下载 Kubernetes
type: docs
---
<!--
title: Download Kubernetes
type: docs
-->

<!--
Kubernetes ships binaries for each component as well as a standard set of client
applications to bootstrap or interact with a cluster. Components like the
API server are capable of running within container images inside of a
cluster. Those components are also shipped in container images as part of the
official release process. All binaries as well as container images are available
for multiple operating systems as well as hardware architectures.
-->
Kubernetes 为每个组件提供二进制文件以及一组标准的客户端应用来引导集群或与集群交互。
像 API 服务器这样的组件能够在集群内的容器镜像中运行。
这些组件作为官方发布过程的一部分，也以容器镜像的形式提供。
所有二进制文件和容器镜像都可用于多种操作系统和硬件架构。

### kubectl

<!-- overview -->

<!--
The Kubernetes command-line tool, [kubectl](/docs/reference/kubectl/kubectl/), allows
you to run commands against Kubernetes clusters.

You can use kubectl to deploy applications, inspect and manage cluster resources,
and view logs. For more information including a complete list of kubectl operations, see the
[`kubectl` reference documentation](/docs/reference/kubectl/).
-->
Kubernetes 命令行工具 [kubectl](/zh-cn/docs/reference/kubectl/kubectl/)
允许你对 Kubernetes 集群执行命令。

你可以使用 kubectl 部署应用，还可以检查和管理集群资源以及查看日志。
有关包括 kubectl 完整操作列表在内的更多信息，请参阅
[`kubectl` 参考文档](/zh-cn/docs/reference/kubectl/)。

<!--
kubectl is installable on a variety of Linux platforms, macOS and Windows.
Find your preferred operating system below.

- [Install kubectl on Linux](/docs/tasks/tools/install-kubectl-linux)
- [Install kubectl on macOS](/docs/tasks/tools/install-kubectl-macos)
- [Install kubectl on Windows](/docs/tasks/tools/install-kubectl-windows)
-->
kubectl 可安装在各种 Linux 平台、macOS 和 Windows 上。
在下方找到你首选的操作系统。

- [在 Linux 上安装 kubectl](/zh-cn/docs/tasks/tools/install-kubectl-linux)
- [在 macOS 上安装 kubectl](/zh-cn/docs/tasks/tools/install-kubectl-macos)
- [在 Windows 上安装 kubectl](/zh-cn/docs/tasks/tools/install-kubectl-windows)

<!--
## Container images

All Kubernetes container images are deployed to the
`registry.k8s.io` container image registry.
-->
## 容器镜像  {#container-images}

所有 Kubernetes 容器镜像都被部署到 `registry.k8s.io` 容器镜像仓库。

<!--
| Container Image                                                           | Supported Architectures          |
-->
| 容器镜像                                                                   | 支持架构                           |
| ------------------------------------------------------------------------- | --------------------------------- |
| registry.k8s.io/kube-apiserver:v{{< skew currentPatchVersion >}}          | amd64, arm, arm64, ppc64le, s390x |
| registry.k8s.io/kube-controller-manager:v{{< skew currentPatchVersion >}} | amd64, arm, arm64, ppc64le, s390x |
| registry.k8s.io/kube-proxy:v{{< skew currentPatchVersion >}}              | amd64, arm, arm64, ppc64le, s390x |
| registry.k8s.io/kube-scheduler:v{{< skew currentPatchVersion >}}          | amd64, arm, arm64, ppc64le, s390x |
| registry.k8s.io/conformance:v{{< skew currentPatchVersion >}}             | amd64, arm, arm64, ppc64le, s390x |

<!--
### Container image architectures
-->
### 容器镜像架构

<!--
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
`registry.k8s.io/kube-apiserver-arm64:v{{< skew currentPatchVersion >}}`. 
-->
所有容器镜像都支持多架构，而容器运行时应根据下层平台选择正确的镜像。
也可以通过给容器镜像名称加后缀来拉取适合特定架构的镜像，例如
`registry.k8s.io/kube-apiserver-arm64:v{{< skew currentPatchVersion >}}`。

<!--
### Container image signatures
-->
### 容器镜像签名

{{< feature-state for_k8s_version="v1.26" state="beta" >}}

<!--
For Kubernetes {{< param "version" >}},
container images are signed using [sigstore](https://sigstore.dev)
signatures:
-->
对于 Kubernetes {{< param "version" >}}，容器镜像使用
[sigstore](https://sigstore.dev) 进行签名：

{{< note >}}
<!--
Container image sigstore signatures do currently not match between different geographical locations.
More information about this problem is available in the corresponding
[GitHub issue](https://github.com/kubernetes/registry.k8s.io/issues/187).
-->
目前，不同地理位置之间的容器镜像 sigstore 签名不匹配。
有关此问题的更多信息，请参阅相应的
[GitHub Issue](https://github.com/kubernetes/registry.k8s.io/issues/187)。
{{< /note >}}


<!--
The Kubernetes project publishes a list of signed Kubernetes container images
in [SPDX 2.3](https://spdx.dev/specifications/) format.
You can fetch that list using:
-->
Kubernetes 项目以 [SPDX 2.3](https://spdx.dev/specifications/) 格式发布已签名的
Kubernetes 容器镜像列表。你可以使用以下方法获取该列表：

```shell
curl -Ls "https://sbom.k8s.io/$(curl -Ls https://dl.k8s.io/release/stable.txt)/release" | grep "SPDXID: SPDXRef-Package-registry.k8s.io" |  grep -v sha256 | cut -d- -f3- | sed 's/-/\//' | sed 's/-v1/:v1/'
```

<!--
To manually verify signed container images of Kubernetes core components, refer to
[Verify Signed Container Images](/docs/tasks/administer-cluster/verify-signed-artifacts).
-->
如需手动验证 Kubernetes 核心组件的签名容器镜像，
请参考[验证签名容器镜像](/zh-cn/docs/tasks/administer-cluster/verify-signed-artifacts)。

<!--
If you pull a container image for a specific architecture, the single-architecture image
is signed in the same way as for the multi-architecture manifest lists.
-->
如果你要拉取特定架构的容器镜像，则单架构镜像的签名方式与多架构清单列表相同。

<!--
## Binaries
-->
## 二进制  {#binaries}

{{< release-binaries >}}