Skip to content

Commit 15d92d1

Browse files
authored
Merge pull request #38871 from windsonsea/upgradey
[zh] sync cluster-upgrade.md
2 parents 01a60ed + 84c6c98 commit 15d92d1

File tree

1 file changed

+34
-33
lines changed

1 file changed

+34
-33
lines changed

content/zh-cn/docs/tasks/administer-cluster/cluster-upgrade.md

Lines changed: 34 additions & 33 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ content_type: task
88
-->
99

1010
<!-- overview -->
11-
<!--
11+
<!--
1212
This page provides an overview of the steps you should follow to upgrade a
1313
Kubernetes cluster.
1414
@@ -23,7 +23,7 @@ At a high level, the steps you perform are:
2323

2424
从高层规划的角度看,要执行的步骤是:
2525

26-
<!--
26+
<!--
2727
- Upgrade the {{< glossary_tooltip text="control plane" term_id="control-plane" >}}
2828
- Upgrade the nodes in your cluster
2929
- Upgrade clients such as {{< glossary_tooltip text="kubectl" term_id="kubectl" >}}
@@ -37,24 +37,26 @@ At a high level, the steps you perform are:
3737

3838
## {{% heading "prerequisites" %}}
3939

40-
<!--
40+
<!--
4141
You must have an existing cluster. This page is about upgrading from Kubernetes
4242
{{< skew currentVersionAddMinor -1 >}} to Kubernetes {{< skew currentVersion >}}. If your cluster
4343
is not currently running Kubernetes {{< skew currentVersionAddMinor -1 >}} then please check
4444
the documentation for the version of Kubernetes that you plan to upgrade to.
4545
-->
4646
你必须有一个集群。
47-
本页内容涉及从 Kubernetes {{< skew currentVersionAddMinor -1 >}}
47+
本页内容涉及从 Kubernetes {{< skew currentVersionAddMinor -1 >}}
4848
升级到 Kubernetes {{< skew currentVersion >}}。
4949
如果你的集群未运行 Kubernetes {{< skew currentVersionAddMinor -1 >}},
5050
那请参考目标 Kubernetes 版本的文档。
5151

52-
<!-- ## Upgrade approaches -->
52+
<!--
53+
## Upgrade approaches
54+
-->
5355
## 升级方法 {#upgrade-approaches}
5456

5557
### kubeadm {#upgrade-kubeadm}
5658

57-
<!--
59+
<!--
5860
If your cluster was deployed using the `kubeadm` tool, refer to
5961
[Upgrading kubeadm clusters](/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/)
6062
for detailed information on how to upgrade the cluster.
@@ -63,58 +65,56 @@ Once you have upgraded the cluster, remember to
6365
[install the latest version of `kubectl`](/docs/tasks/tools/).
6466
-->
6567
如果你的集群是使用 `kubeadm` 安装工具部署而来,
66-
那么升级集群的详细信息,请参阅
67-
[升级 kubeadm 集群](/zh-cn/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/)
68+
那么升级集群的详细信息,请参阅[升级 kubeadm 集群](/zh-cn/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/)
6869

69-
升级集群之后,要记得
70-
[安装最新版本的 `kubectl`](/zh-cn/docs/tasks/tools/).
70+
升级集群之后,要记得[安装最新版本的 `kubectl`](/zh-cn/docs/tasks/tools/)
7171

72-
<!-- ### Manual deployments -->
72+
<!--
73+
### Manual deployments
74+
-->
7375
### 手动部署 {#manual-deployments}
7476

75-
<!--
77+
{{< caution >}}
78+
<!--
7679
These steps do not account for third-party extensions such as network and storage
7780
plugins.
78-
79-
You should manually update the control plane following this sequence:
8081
-->
81-
{{< caution >}}
82-
这些步骤不考虑第三方扩展,例如网络和存储插件。
82+
这些步骤不考虑网络和存储插件等第三方扩展。
8383
{{< /caution >}}
8484

85-
你应该跟随下面操作顺序,手动更新控制平面:
85+
<!--
86+
You should manually update the control plane following this sequence:
8687
87-
<!--
8888
- etcd (all instances)
8989
- kube-apiserver (all control plane hosts)
9090
- kube-controller-manager
9191
- kube-scheduler
9292
- cloud controller manager, if you use one
9393
-->
94+
你应该按照下面的操作顺序,手动更新控制平面:
95+
9496
- etcd (所有实例)
9597
- kube-apiserver (所有控制平面的宿主机)
9698
- kube-controller-manager
9799
- kube-scheduler
98100
- cloud controller manager (在你用到时)
99101

100-
<!--
102+
<!--
101103
At this point you should
102104
[install the latest version of `kubectl`](/docs/tasks/tools/).
103105
104106
For each node in your cluster, [drain](/docs/tasks/administer-cluster/safely-drain-node/)
105107
that node and then either replace it with a new node that uses the {{< skew currentVersion >}}
106-
kubelet, or upgrade the {{< skew currentVersion >}}
107-
kubelet on that node and bring the node back into service.
108+
kubelet, or upgrade the kubelet on that node and bring the node back into service.
108109
-->
109-
现在,你应该
110-
[安装最新版本的 `kubectl`](/zh-cn/docs/tasks/tools/).
110+
现在,你应该[安装最新版本的 `kubectl`](/zh-cn/docs/tasks/tools/)
111111

112112
对于集群中的每个节点,
113-
首先需要[腾空](/zh-cn/docs/tasks/administer-cluster/safely-drain-node/)
114-
节点,然后使用一个运行了 kubelet {{< skew currentVersion >}} 版本的新节点替换它;
113+
首先需要[腾空](/zh-cn/docs/tasks/administer-cluster/safely-drain-node/)节点,
114+
然后使用一个运行了 kubelet {{< skew currentVersion >}} 版本的新节点替换它;
115115
或者升级此节点的 kubelet,并使节点恢复服务。
116116

117-
<!--
117+
<!--
118118
### Other deployments {#upgrade-other}
119119
120120
Refer to the documentation for your cluster deployment tool to learn the recommended set
@@ -132,7 +132,7 @@ up steps for maintenance.
132132

133133
### 切换集群的存储 API 版本 {#switch-your-clusters-storage-api-version}
134134

135-
<!--
135+
<!--
136136
The objects that are serialized into etcd for a cluster's internal
137137
representation of the Kubernetes resources active in the cluster are
138138
written using a particular version of the API.
@@ -152,7 +152,7 @@ write it back also using the latest supported API.
152152

153153
对于每个受影响的对象,请使用最新支持的 API 读取它,然后使用所支持的最新 API 将其写回。
154154

155-
<!--
155+
<!--
156156
### Update manifests
157157
158158
Upgrading to a new Kubernetes version can provide new APIs.
@@ -171,7 +171,7 @@ For example:
171171
kubectl convert -f pod.yaml --output-version v1
172172
```
173173

174-
<!--
174+
<!--
175175
The `kubectl` tool replaces the contents of `pod.yaml` with a manifest that sets `kind` to
176176
Pod (unchanged), but with a revised `apiVersion`.
177177
-->
@@ -187,13 +187,14 @@ release with a newer device plugin API version, device plugins must be upgraded
187187
both version before the node is upgraded in order to guarantee that device allocations
188188
continue to complete successfully during the upgrade.
189189
190-
Refer to [API compatiblity](docs/concepts/extend-kubernetes/compute-storage-net/device-plugins.md/#api-compatibility) and [Kubelet Device Manager API Versions](docs/reference/node/device-plugin-api-versions.md) for more details.
190+
Refer to [API compatibility](/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/#api-compatibility) and [Kubelet Device Manager API Versions](/docs/reference/node/device-plugin-api-versions/) for more details.
191191
-->
192192
### 设备插件 {#device-plugins}
193193

194-
如果你的集群正在运行设备插件(Device Plugins)并且节点需要升级到具有更新的设备插件(Device Plugins
194+
如果你的集群正在运行设备插件(Device Plugin)并且节点需要升级到具有更新的设备插件(Device Plugin
195195
API 版本的 Kubernetes 版本,则必须在升级节点之前升级设备插件以同时支持这两个插件 API 版本,
196196
以确保升级过程中设备分配能够继续成功完成。
197197

198-
有关详细信息,请参阅 [API 兼容性](/zh-cn/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins.md/#api-compatibility)
199-
[kubelet 设备管理器 API 版本](/zh-cn/docs/reference/node/device-plugin-api-versions.md)
198+
有关详细信息,请参阅
199+
[API 兼容性](/zh-cn/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/#api-compatibility)
200+
[kubelet 设备管理器 API 版本](/zh-cn/docs/reference/node/device-plugin-api-versions/)

0 commit comments

Comments
 (0)