From edff1c8535fb189c7785101a9691078cfb1f532d Mon Sep 17 00:00:00 2001
From: luzg <hikube@163.com>
Date: Sun, 22 Nov 2020 22:55:08 +0800
Subject: [PATCH] [zh] Translate task cluster-upgrade

---
 .../administer-cluster/cluster-upgrade.md     | 182 ++++++++++++++++++
 1 file changed, 182 insertions(+)
 create mode 100644 content/zh/docs/tasks/administer-cluster/cluster-upgrade.md

diff --git a/content/zh/docs/tasks/administer-cluster/cluster-upgrade.md b/content/zh/docs/tasks/administer-cluster/cluster-upgrade.md
new file mode 100644
index 0000000000..e9b9d0dec5
--- /dev/null
+++ b/content/zh/docs/tasks/administer-cluster/cluster-upgrade.md
@@ -0,0 +1,182 @@
+---
+title: 升级集群
+content_type: task
+---
+<!-- 
+---
+title: Upgrade A Cluster
+content_type: task
+---
+-->
+
+<!-- overview -->
+<!-- 
+This page provides an overview of the steps you should follow to upgrade a
+Kubernetes cluster.
+
+The way that you upgrade a cluster depends on how you initially deployed it
+and on any subsequent changes.
+
+At a high level, the steps you perform are:
+-->
+本页概述升级 Kubernetes 集群的步骤。
+
+升级集群的方式取决于你最初部署它的方式、以及后续更改它的方式。
+
+从高层规划的角度看，要执行的步骤是：
+
+<!-- 
+- Upgrade the {{< glossary_tooltip text="control plane" term_id="control-plane" >}}
+- Upgrade the nodes in your cluster
+- Upgrade clients such as {{< glossary_tooltip text="kubectl" term_id="kubectl" >}}
+- Adjust manifests and other resources based on the API changes that accompany the
+  new Kubernetes version
+-->
+- 升级{{< glossary_tooltip text="控制平面" term_id="control-plane" >}}
+- 升级集群中的节点
+- 升级 {{< glossary_tooltip text="kubectl" term_id="kubectl" >}} 之类的客户端
+- 根据新 Kubernetes 版本带来的 API 变化，调整清单文件和其他资源
+
+## {{% heading "prerequisites" %}}
+
+<!-- 
+You must have an existing cluster. This page is about upgrading from Kubernetes
+{{< skew prevMinorVersion >}} to Kubernetes {{< skew latestVersion >}}. If your cluster
+is not currently running Kubernetes {{< skew prevMinorVersion >}} then please check
+the documentation for the version of Kubernetes that you plan to upgrade to.
+-->
+你必须有一个集群。
+本页内容涉及从 Kubernetes {{< skew prevMinorVersion >}} 
+升级到 Kubernetes {{< skew latestVersion >}}。
+如果你的集群未运行 Kubernetes {{< skew prevMinorVersion >}}，
+那请参考目标 Kubernetes 版本的文档。
+
+<!-- ## Upgrade approaches -->
+## 升级方法 {#upgrade-approaches}
+
+### kubeadm {#upgrade-kubeadm}
+
+<!-- 
+If your cluster was deployed using the `kubeadm` tool, refer to 
+[Upgrading kubeadm clusters](/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/)
+for detailed information on how to upgrade the cluster.
+
+Once you have upgraded the cluster, remember to
+[install the latest version of `kubectl`](/docs/tasks/tools/install-kubectl/).
+-->
+如果你的集群是使用 `kubeadm` 安装工具部署而来，
+那么升级群集的详细信息，请参阅
+[升级 kubeadm 集群](/zh/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/)。
+
+升级集群之后，要记得
+[安装最新版本的 `kubectl`](/zh/docs/tasks/tools/install-kubectl/).
+
+<!-- ### Manual deployments -->
+### 手动部署 {#manual-deployments}
+
+<!-- 
+These steps do not account for third-party extensions such as network and storage
+plugins.
+
+You should manually update the control plane following this sequence:
+-->
+{{< caution >}}
+这些步骤不考虑第三方扩展，例如网络和存储插件。
+{{< /caution >}}
+
+你应该跟随下面操作顺序，手动更新控制平面：
+
+<!-- 
+- etcd (all instances)
+- kube-apiserver (all control plane hosts)
+- kube-controller-manager
+- kube-scheduler
+- cloud controller manager, if you use one
+-->
+- etcd (所有实例)
+- kube-apiserver (所有控制平面的宿主机)
+- kube-controller-manager
+- kube-scheduler
+- cloud controller manager, 在你用到时
+
+<!-- 
+At this point you should
+[install the latest version of `kubectl`](/docs/tasks/tools/install-kubectl/).
+
+For each node in your cluster, [drain](/docs/tasks/administer-cluster/safely-drain-node/)
+that node and then either replace it with a new node that uses the {{< skew latestVersion >}}
+kubelet, or upgrade the {{< skew latestVersion >}}
+kubelet on that node and bring the node back into service.
+-->
+现在，你应该
+[安装最新版本的 `kubectl`](/zh/docs/tasks/tools/install-kubectl/).
+
+对于群集中的每个节点，
+[排空](/zh/docs/tasks/administer-cluster/safely-drain-node/)
+节点，然后，或者用一个运行了 {{< skew latestVersion >}} kubelet 的新节点替换它；
+或者升级此节点的 kubelet，并使节点恢复服务。
+
+<!-- 
+### Other deployments {#upgrade-other}
+
+Refer to the documentation for your cluster deployment tool to learn the recommended set
+up steps for maintenance.
+
+## Post-upgrade tasks
+
+### Switch your cluster's storage API version
+-->
+### 其他部署方式 {#upgrade-other}
+
+参阅你的集群部署工具对应的文档，了解用于维护的推荐设置步骤。
+
+## 升级后的任务 {#post-upgrade-tasks}
+
+### 切换群集的存储 API 版本 {#switch-your-clusters-storage-api-version}
+
+<!-- 
+The objects that are serialized into etcd for a cluster's internal
+representation of the Kubernetes resources active in the cluster are
+written using a particular version of the API.
+
+When the supported API changes, these objects may need to be rewritten
+in the newer API. Failure to do this will eventually result in resources
+that are no longer decodable or usable by the Kubernetes API server.
+
+For each affected object, fetch it using the latest supported API and then
+write it back also using the latest supported API.
+-->
+对象序列化到 etcd，是为了提供集群中活动 Kubernetes 资源的内部表示法，
+这些对象都使用特定版本的 API 编写。
+
+当底层的 API 更改时，这些对象可能需要用新 API 重写。
+如果不能做到这一点，会导致再也不能用 Kubernetes API 服务器解码、使用该对象。
+
+对于每个受影响的对象，用最新支持的 API 获取它，然后再用最新支持的 API 写回来。
+
+<!-- 
+### Update manifests
+
+Upgrading to a new Kubernetes version can provide new APIs.
+
+You can use `kubectl convert` command to convert manifests between different API versions.
+For example:
+-->
+### 更新清单 {#update-manifests}
+
+升级到新版本 Kubernetes 就可以提供新的 API。
+
+你可以使用 `kubectl convert` 命令在不同 API 版本之间转换清单。
+例如：
+
+```shell
+kubectl convert -f pod.yaml --output-version v1
+```
+
+<!-- 
+The `kubectl` tool replaces the contents of `pod.yaml` with a manifest that sets `kind` to
+Pod (unchanged), but with a revised `apiVersion`.
+-->
+`kubectl` 替换了 `pod.yaml` 的内容，
+在新的清单文件中，`kind` 被设置为 Pod（未变），
+但 `apiVersion` 则被修订了。