Change:
--- --> <del> {{% capture overview %}} </del> <!-- <del> This document outlines the various binary components needed to deliver a functioning Kubernetes cluster. </del> <ins> When you deploy Kubernetes, you get a cluster. {{< glossary_definition term_id="cluster" length="all" prepend="A Kubernetes cluster consists of">}} This document outlines the various components you need to have a complete and working Kubernetes cluster. Here's the diagram of a Kubernetes cluster with all the components tied together. ![Components of Kubernetes](/images/docs/components-of-kubernetes.png) </ins> --> <del> 本文档概述了交付正常运行的 Kubernetes 集群所需的各种二进制组件。 </del> <ins> {{% capture overview %}} 当你部署完 Kubernetes, 即拥有了一个完整的集群。 {{< glossary_definition term_id="cluster" length="all" prepend="一个 Kubernetes 集群包含">}} 本文档概述了交付正常运行的 Kubernetes 集群所需的各种组件。 这张图表展示了包含所有相互关联组件的 Kubernetes 集群。 ![Components of Kubernetes](/images/docs/components-of-kubernetes.png) </ins> {{% /capture %}} {{% capture body %}} <del> <!-- ## Master Components </del> <ins> <!-- ## Control Plane Components </ins> --> <del> ## Master 组件 </del> <ins> ## 控制平面组件（Control Plane Components） </ins> <del> <!-- Master components provide the cluster's control plane. Master components make global decisions about the cluster (for example, scheduling), and they detect and respond to cluster events (for example, starting up a new {{< glossary_tooltip text="pod" term_id="pod">}} when a deployment's `replicas` field is unsatisfied). --> Master 组件提供集群的控制平面。Master 组件对集群进行全局决策（例如，调度），并检测和响应集群事件（例如，当不满足部署的 `replicas` 字段时，启动新的 {{< glossary_tooltip text="pod" term_id="pod">}}）。 </del> <ins> <!-- The Control Plane's components make global decisions about the cluster (for example, scheduling), as well as detecting and responding to cluster events (for example, starting up a new {{< glossary_tooltip text="pod" term_id="pod">}} when a deployment's `replicas` field is unsatisfied). --> 控制平面的组件对集群做出全局决策(比如调度)，以及检测和响应集群事件（例如，当不满足部署的 `replicas` 字段时，启动新的 {{< glossary_tooltip text="pod" term_id="pod">}}）。 </ins> <del> <!-- Master components can be run on any machine in the cluster. However, for simplicity, set up scripts typically start all master components on </del> <ins> <!-- Control Plane components can be run on any machine in the cluster. However, for simplicity, set up scripts typically start all Control Plane components on </ins> the same machine, and do not run user containers on this machine. See [Building High-Availability Clusters](/docs/admin/high-availability/) for an example multi-master-VM setup. <del> --> Master 组件可以在集群中的任何节点上运行。然而，为了简单起见，安装脚本通常会启动同一个计算机上所有 Master 组件，并且不会在计算机上运行用户容器。请参阅[构建高可用性集群](/docs/admin/high-availability/)示例对于多主机 VM 的安装。 </del> <ins> --> 控制平面组件可以在集群中的任何节点上运行。然而，为了简单起见，安装脚本通常会启动同一个计算机上所有控制平面组件，并且不会在计算机上运行用户容器。请参阅[构建高可用性集群](/docs/admin/high-availability/)示例对于多主机 VM 的安装。 </ins> ### kube-apiserver

Discussion:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: Too many content missing and incorrect translation while marked as the latest 1.16 version documents in Chinese. For example: "However, for simplicity, set up scripts typically start all master components on the same machine" "the same machine" in English has been translated to "the same virtual machine" in Chinese. Proposed Solution: Have some body review the Chinese version translation or mark it as a outdate version translation Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language zh
WIP /assign
any progress?
Sorry for the delay. Update has been pushed.