Merge pull request #34585 from tengqm/zh-resync-createcluster
[zh-cn] Resync cerate cluster using kubeadm
This commit is contained in:
+29
-24
@@ -970,12 +970,13 @@ Kubernetes 版本可以通过使用 `--kubeadm init` 的 `--kubernetes-version`
|
||||
|
||||
<!--
|
||||
Example:
|
||||
* kubeadm is at {{< skew latestVersion >}}
|
||||
* `kubernetesVersion` must be at {{< skew latestVersion >}} or {{< skew prevMinorVersion >}}
|
||||
* kubeadm is at {{< skew currentVersion >}}
|
||||
* `kubernetesVersion` must be at {{< skew currentVersion >}} or {{< skew currentVersionAddMinor -1 >}}
|
||||
-->
|
||||
例子:
|
||||
* kubeadm 的版本为 {{< skew latestVersion >}}。
|
||||
* `kubernetesVersion` 必须为 {{< skew latestVersion >}} 或者 {{< skew prevMinorVersion >}}。
|
||||
|
||||
* kubeadm 的版本为 {{< skew currentVersion >}}。
|
||||
* `kubernetesVersion` 必须为 {{< skew currentVersion >}} 或者 {{< skew currentVersionAddMinor -1 >}}。
|
||||
|
||||
<!--
|
||||
### kubeadm's skew against the kubelet
|
||||
@@ -991,12 +992,13 @@ version as kubeadm or one version older.
|
||||
|
||||
<!--
|
||||
Example:
|
||||
* kubeadm is at {{< skew latestVersion >}}
|
||||
* kubelet on the host must be at {{< skew latestVersion >}} or {{< skew prevMinorVersion >}}
|
||||
* kubeadm is at {{< skew currentVersion >}}
|
||||
* kubelet on the host must be at {{< skew currentVersion >}} or {{< skew currentVersionAddMinor -1 >}}
|
||||
-->
|
||||
例子:
|
||||
* kubeadm 的版本为 {{< skew latestVersion >}}
|
||||
* 主机上的 kubelet 版本必须为 {{< skew latestVersion >}} 或者 {{< skew prevMinorVersion >}}
|
||||
|
||||
* kubeadm 的版本为 {{< skew currentVersion >}}。
|
||||
* 主机上的 kubelet 必须为 {{< skew currentVersion >}} 或者 {{< skew currentVersionAddMinor -1 >}}。
|
||||
|
||||
<!--
|
||||
### kubeadm's skew against kubeadm
|
||||
@@ -1021,12 +1023,13 @@ with the exception of `kubeadm upgrade`.
|
||||
|
||||
<!--
|
||||
Example for `kubeadm join`:
|
||||
* kubeadm version {{< skew latestVersion >}} was used to create a cluster with `kubeadm init`
|
||||
* Joining nodes must use a kubeadm binary that is at version {{< skew latestVersion >}}
|
||||
* kubeadm version {{< skew currentVersion >}} was used to create a cluster with `kubeadm init`
|
||||
* Joining nodes must use a kubeadm binary that is at version {{< skew currentVersion >}}
|
||||
-->
|
||||
`kubeadm join` 的例子:
|
||||
* 使用 `kubeadm init` 创建集群时使用版本为 {{< skew latestVersion >}} 的 kubeadm。
|
||||
* 加入的节点必须使用版本为 {{< skew latestVersion >}} 的 kubeadm 二进制文件。
|
||||
|
||||
* 使用 `kubeadm init` 创建集群时使用版本为 {{< skew currentVersion >}} 的 kubeadm。
|
||||
* 添加节点所用的 kubeadm 可执行文件为版本 {{< skew currenttVersion >}}。
|
||||
|
||||
<!--
|
||||
Nodes that are being upgraded must use a version of kubeadm that is the same MINOR
|
||||
@@ -1038,13 +1041,13 @@ MINOR 版本或比后者新一个 MINOR 版本。
|
||||
|
||||
<!--
|
||||
Example for `kubeadm upgrade`:
|
||||
* kubeadm version {{< skew prevMinorVersion >}} was used to create or upgrade the node
|
||||
* The version of kubeadm used for upgrading the node must be at {{< skew prevMinorVersion >}}
|
||||
or {{< skew latestVersion >}}
|
||||
* kubeadm version {{< skew currentVersionAddMinor -1 >}} was used to create or upgrade the node
|
||||
* The version of kubeadm used for upgrading the node must be at {{< skew currentVersionAddMinor -1 >}}
|
||||
or {{< skew currentVersion >}}
|
||||
-->
|
||||
`kubeadm upgrade` 的例子:
|
||||
* 用于创建或升级节点的 kubeadm 版本为 {{< skew prevMinorVersion >}}。
|
||||
* 用于升级节点的 kubeadm 版本必须为 {{< skew prevMinorVersion >}} 或 {{< skew latestVersion >}}。
|
||||
* 用于创建或升级节点的 kubeadm 版本为 {{< skew currentVersionAddMinor -1 >}}。
|
||||
* 用于升级节点的 kubeadm 版本必须为 {{< skew currentVersionAddMinor -1 >}} 或 {{< skew currentVersion >}}。
|
||||
|
||||
<!--
|
||||
To learn more about the version skew between the different Kubernetes component see
|
||||
@@ -1055,12 +1058,11 @@ the [Version Skew Policy](https://kubernetes.io/releases/version-skew-policy/).
|
||||
|
||||
<!--
|
||||
## Limitations {#limitations}
|
||||
|
||||
### Cluster resilience {#resilience}
|
||||
-->
|
||||
## 局限性 {#limitations}
|
||||
|
||||
<!--
|
||||
### Cluster resilience {#resilience}
|
||||
-->
|
||||
### 集群弹性 {#resilience}
|
||||
|
||||
<!--
|
||||
@@ -1100,9 +1102,10 @@ Workarounds:
|
||||
<!--
|
||||
kubeadm deb/rpm packages and binaries are built for amd64, arm (32-bit), arm64, ppc64le, and s390x
|
||||
following the [multi-platform
|
||||
proposal](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/multi-platform.md).
|
||||
proposal](https://git.k8s.io/design-proposals-archive/multi-platform.md).
|
||||
-->
|
||||
kubeadm deb/rpm 软件包和二进制文件是为 amd64、arm (32-bit)、arm64、ppc64le 和 s390x 构建的遵循[多平台提案](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/multi-platform.md)。
|
||||
kubeadm deb/rpm 软件包和二进制文件是为 amd64、arm (32-bit)、arm64、ppc64le 和 s390x
|
||||
构建的遵循[多平台提案](https://git.k8s.io/design-proposals-archive/multi-platform.md)。
|
||||
|
||||
<!--
|
||||
Multiplatform container images for the control plane and addons are also supported since v1.12.
|
||||
@@ -1114,7 +1117,8 @@ Only some of the network providers offer solutions for all platforms. Please con
|
||||
network providers above or the documentation from each provider to figure out whether the provider
|
||||
supports your chosen platform.
|
||||
-->
|
||||
只有一些网络提供商为所有平台提供解决方案。请查阅上方的网络提供商清单或每个提供商的文档以确定提供商是否支持你选择的平台。
|
||||
只有一些网络提供商为所有平台提供解决方案。
|
||||
请查阅上方的网络提供商清单或每个提供商的文档以确定提供商是否支持你选择的平台。
|
||||
|
||||
<!--
|
||||
## Troubleshooting {#troubleshooting}
|
||||
@@ -1124,4 +1128,5 @@ supports your chosen platform.
|
||||
<!--
|
||||
If you are running into difficulties with kubeadm, please consult our [troubleshooting docs](/docs/setup/production-environment/tools/kubeadm/troubleshooting-kubeadm/).
|
||||
-->
|
||||
如果你在使用 kubeadm 时遇到困难,请查阅我们的[故障排除文档](/zh-cn/docs/setup/production-environment/tools/kubeadm/troubleshooting-kubeadm/)。
|
||||
如果你在使用 kubeadm 时遇到困难,
|
||||
请查阅我们的[故障排除文档](/zh-cn/docs/setup/production-environment/tools/kubeadm/troubleshooting-kubeadm/)。
|
||||
|
||||
Reference in New Issue
Block a user