Merge pull request #47660 from my-git9/pp-13335

[zh-cn] sync working-with-objects/components.md

Author: k8s-ci-robot

content/zh-cn/docs/concepts/overview/components.md

@@ -2,7 +2,7 @@
 title: Kubernetes 组件
 content_type: concept
 description: >
-  Kubernetes 集群由控制平面的组件和一组称为节点的机器组成。
+  组成 Kubernetes 集群的关键组件概述。
 weight: 30
 card:
   title: 集群组件
@@ -15,8 +15,7 @@ reviewers:
 title: Kubernetes Components
 content_type: concept
 description: >
-  A Kubernetes cluster consists of the components that are a part of the control
-  plane and a set of machines called nodes.
+  An overview of the key components that make up a Kubernetes cluster.
 weight: 30
 card:
   title: Components of a cluster
@@ -27,256 +26,145 @@ card:
 <!-- overview -->
 
 <!--
-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 for
-a complete and working Kubernetes cluster.
+本页面概述了组成 Kubernetes 集群的基本组件。
 
 {{ < figure src="/images/docs/components-of-kubernetes.svg" alt="Components of Kubernetes" caption="The components of a Kubernetes cluster" class="diagram-large" clicktozoom="true" >}}
 -->
-当你部署完 Kubernetes，便拥有了一个完整的集群。
-
-{{< glossary_definition term_id="cluster" length="all" >}}
-
 本文档概述了一个正常运行的 Kubernetes 集群所需的各种组件。
 
 {{< figure src="/images/docs/components-of-kubernetes.svg" alt="Kubernetes 的组件" caption="Kubernetes 集群的组件" class="diagram-large" clicktozoom="true" >}}
 
 <!-- body -->
 
 <!--
-## Control Plane Components
-
-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
-`{{< glossary_tooltip text="replicas" term_id="replica" >}}` field is unsatisfied).
- -->
-## 控制平面组件（Control Plane Components）    {#control-plane-components}
+## Core Components
 
-控制平面组件会为集群做出全局决策，比如资源的调度。
-以及检测和响应集群事件，例如当不满足部署的 `{{< glossary_tooltip text="replicas" term_id="replica" >}}`
-字段时，要启动新的 {{< glossary_tooltip text="Pod" term_id="pod">}}）。
-
-<!--
-Control plane components can be run on any machine in the cluster. However,
-for simplicity, setup scripts typically start all control plane components on
-the same machine, and do not run user containers on this machine. See
-[Creating Highly Available clusters with kubeadm](/docs/setup/production-environment/tools/kubeadm/high-availability/)
-for an example control plane setup that runs across multiple machines.
+A Kubernetes cluster consists of a control plane and one or more worker nodes. Here's a brief overview of the main components:
 -->
-控制平面组件可以在集群中的任何节点上运行。
-然而，为了简单起见，设置脚本通常会在同一个计算机上启动所有控制平面组件，
-并且不会在此计算机上运行用户容器。
-请参阅[使用 kubeadm 构建高可用性集群](/zh-cn/docs/setup/production-environment/tools/kubeadm/high-availability/)
-中关于跨多机器控制平面设置的示例。
-
-### kube-apiserver
-
-{{< glossary_definition term_id="kube-apiserver" length="all" >}}
-
-### etcd
+## 核心组件
 
-{{< glossary_definition term_id="etcd" length="all" >}}
+Kubernetes 集群由控制平面和一个或多个工作节点组成。以下是主要组件的简要概述：
 
-### kube-scheduler
+<!--
+### Control Plane Components
 
-{{< glossary_definition term_id="kube-scheduler" length="all" >}}
+Manage the overall state of the cluster:
 
-### kube-controller-manager
+[kube-apiserver](/docs/concepts/architecture/#kube-apiserver)
+: The core component server that exposes the Kubernetes HTTP API
 
-{{< glossary_definition term_id="kube-controller-manager" length="all" >}}
+[etcd](/docs/concepts/architecture/#etcd)
+: Consistent and highly-available key value store for all API server data
 
-<!--
-There are many different types of controllers. Some examples of them are:
+[kube-scheduler](/docs/concepts/architecture/#kube-scheduler)
+: Looks for Pods not yet bound to a node, and assigns each Pod to a suitable node.
 
-  * Node controller: Responsible for noticing and responding when nodes go down.
-  * Job controller: Watches for Job objects that represent one-off tasks, then creates
-    Pods to run those tasks to completion.
-  * EndpointSlice controller: Populates EndpointSlice objects (to provide a link between Services and Pods).
-  * ServiceAccount controller: Create default ServiceAccounts for new namespaces.
+[kube-controller-manager](/docs/concepts/architecture/#kube-controller-manager)
+: Runs {{< glossary_tooltip text="controllers" term_id="controller" >}} to implement Kubernetes API behavior.
 
-The above is not an exhaustive list.
+[cloud-controller-manager](/docs/concepts/architecture/#cloud-controller-manager) (optional)
+: Integrates with underlying cloud provider(s)
 -->
-有许多不同类型的控制器。以下是一些例子：
-
-* 节点控制器（Node Controller）：负责在节点出现故障时进行通知和响应
-* 任务控制器（Job Controller）：监测代表一次性任务的 Job 对象，然后创建 Pod 来运行这些任务直至完成
-* 端点分片控制器（EndpointSlice controller）：填充端点分片（EndpointSlice）对象（以提供 Service 和 Pod 之间的链接）。
-* 服务账号控制器（ServiceAccount controller）：为新的命名空间创建默认的服务账号（ServiceAccount）。
+## 控制平面组件（Control Plane Components）    {#control-plane-components}
 
-以上并不是一个详尽的列表。
-<!--
-### cloud-controller-manager
+管理集群的整体状态：
 
-The cloud-controller-manager only runs controllers that are specific to your cloud provider.
-If you are running Kubernetes on your own premises, or in a learning environment inside your
-own PC, the cluster does not have a cloud controller manager.
+[kube-apiserver](/zh-cn/docs/concepts/architecture/#kube-apiserver)
+: 公开 Kubernetes HTTP API 的核心组件服务器
 
-As with the kube-controller-manager, the cloud-controller-manager combines several logically
-independent control loops into a single binary that you run as a single process. You can
-scale horizontally (run more than one copy) to improve performance or to help tolerate failures.
+[etcd](/zh-cn/docs/concepts/architecture/#etcd)
+: 具备一致性和高可用性的键值存储，用于所有 API 服务器的数据存储
 
-The following controllers can have cloud provider dependencies:
+[kube-scheduler](/zh-cn/docs/concepts/architecture/#kube-scheduler)
+: 查找尚未绑定到节点的 Pod，并将每个 Pod 分配给合适的节点。
 
-  * Node controller: For checking the cloud provider to determine if a node has been deleted in the cloud after it stops responding
-  * Route controller: For setting up routes in the underlying cloud infrastructure
-  * Service controller: For creating, updating and deleting cloud provider load balancers
--->
-### cloud-controller-manager
+[kube-controller-manager](/zh-cn/docs/concepts/architecture/#kube-controller-manager)
+: 运行{{< glossary_tooltip text="控制器" term_id="controller" >}}来实现 Kubernetes API 行为。
 
-{{< glossary_definition term_id="cloud-controller-manager" length="short" >}}
+[cloud-controller-manager](/zh-cn/docs/concepts/architecture/#cloud-controller-manager) (optional)
+: 与底层云驱动集成
 
-`cloud-controller-manager` 仅运行特定于云平台的控制器。
-因此如果你在自己的环境中运行 Kubernetes，或者在本地计算机中运行学习环境，
-所部署的集群不需要有云控制器管理器。
+<!--
+### Node Components
 
-与 `kube-controller-manager` 类似，`cloud-controller-manager`
-将若干逻辑上独立的控制回路组合到同一个可执行文件中，
-供你以同一进程的方式运行。
-你可以对其执行水平扩容（运行不止一个副本）以提升性能或者增强容错能力。
+Run on every node, maintaining running pods and providing the Kubernetes runtime environment:
 
-下面的控制器都包含对云平台驱动的依赖：
+[kubelet](/docs/concepts/architecture/#kubelet)
+: Ensures that Pods are running, including their containers.
 
-  * 节点控制器（Node Controller）：用于在节点终止响应后检查云提供商以确定节点是否已被删除
-  * 路由控制器（Route Controller）：用于在底层云基础架构中设置路由
-  * 服务控制器（Service Controller）：用于创建、更新和删除云提供商负载均衡器
+[kube-proxy](/docs/concepts/architecture/#kube-proxy) (optional)
+: Maintains network rules on nodes to implement {{< glossary_tooltip text="Services" term_id="service" >}}
 
-<!--
-## Node Components
 
-Node components run on every node, maintaining running pods and providing the Kubernetes runtime environment.
+[Container runtime](/docs/concepts/architecture/#container-runtime)
+: Software responsible for running containers. Read [Container Runtimes](/docs/setup/production-environment/container-runtimes/) to learn more.
 -->
 ## Node 组件  {#node-components}
 
-节点组件会在每个节点上运行，负责维护运行的 Pod 并提供 Kubernetes 运行环境。
+在每个节点上运行，维护运行的 Pod 并提供 Kubernetes 运行时环境：
 
-### kubelet
+[kubelet](/zh-cn/docs/concepts/architecture/#kubelet)
+: 确保 Pod 及其容器正常运行。
 
-{{< glossary_definition term_id="kubelet" length="all" >}}
+[kube-proxy](/zh-cn/docs/concepts/architecture/#kube-proxy)（可选）
+: 维护节点上的网络规则以实现 Service 的功能。
 
-### kube-proxy
+[容器运行时（Container runtime）](/zh-cn/docs/concepts/architecture/#container-runtime)
+: 负责运行容器的软件，阅读[容器运行时](/zh-cn/docs/setup/production-environment/container-runtimes/)以了解更多信息。
 
-{{< glossary_definition term_id="kube-proxy" length="all" >}}
+{{% thirdparty-content single="true" %}}
 
 <!--
-### Container runtime
+Your cluster may require additional software on each node; for example, you might also
+run [systemd](https://systemd.io/) on a Linux node to supervise local components.
 -->
-### 容器运行时（Container Runtime）    {#container-runtime}
-
-{{< glossary_definition term_id="container-runtime" length="all" >}}
+你的集群可能需要每个节点上运行额外的软件；例如，你可能还需要在 Linux
+节点上运行 [systemd](https://systemd.io/) 来监督本地组件。
 
 <!--
 ## Addons
 
-Addons use Kubernetes resources ({{< glossary_tooltip term_id="daemonset" >}},
-{{< glossary_tooltip term_id="deployment" >}}, etc)
-to implement cluster features. Because these are providing cluster-level features, namespaced resources
-for addons belong within the `kube-system` namespace.
+Addons extend the functionality of Kubernetes. A few important examples include:
 -->
 ## 插件（Addons）    {#addons}
 
-插件使用 Kubernetes 资源（{{< glossary_tooltip text="DaemonSet" term_id="daemonset" >}}、
-{{< glossary_tooltip text="Deployment" term_id="deployment" >}} 等）实现集群功能。
-因为这些插件提供集群级别的功能，插件中命名空间域的资源属于 `kube-system` 命名空间。
+插件扩展了 Kubernetes 的功能。一些重要的例子包括：
 
 <!--
-Selected addons are described below; for an extended list of available addons, please
-see [Addons](/docs/concepts/cluster-administration/addons/).
--->
-下面描述众多插件中的几种。有关可用插件的完整列表，请参见
-[插件（Addons）](/zh-cn/docs/concepts/cluster-administration/addons/)。
+[DNS](/docs/concepts/architecture/#dns)
+: For cluster-wide DNS resolution
 
-<!--
-### DNS
-
-While the other addons are not strictly required, all Kubernetes clusters should have
-[cluster DNS](/docs/concepts/services-networking/dns-pod-service/), as many examples rely on it.
+[Web UI](/docs/concepts/architecture/#web-ui-dashboard) (Dashboard)
+: For cluster management via a web interface
 
-Cluster DNS is a DNS server, in addition to the other DNS server(s) in your environment,
-which serves DNS records for Kubernetes services.
+[Container Resource Monitoring](/docs/concepts/architecture/#container-resource-monitoring)
+: For collecting and storing container metrics
 
-Containers started by Kubernetes automatically include this DNS server in their DNS searches.
+[Cluster-level Logging](/docs/concepts/architecture/#cluster-level-logging)
+: For saving container logs to a central log store
 -->
-### DNS   {#dns}
+[DNS](/zh-cn/docs/concepts/architecture/#dns)
+: 集群范围内的 DNS 解析
 
-尽管其他插件都并非严格意义上的必需组件，但几乎所有 Kubernetes
-集群都应该有[集群 DNS](/zh-cn/docs/concepts/services-networking/dns-pod-service/)，
-因为很多示例都需要 DNS 服务。
+[Web 界面](/zh-cn/docs/concepts/architecture/#web-ui-dashboard)（Dashboard）
+: 通过 Web 界面进行集群管理
 
-集群 DNS 是一个 DNS 服务器，和环境中的其他 DNS 服务器一起工作，它为 Kubernetes 服务提供 DNS 记录。
+[容器资源监控](/zh-cn/docs/concepts/architecture/#container-resource-monitoring)
+: 用于收集和存储容器指标
 
-Kubernetes 启动的容器自动将此 DNS 服务器包含在其 DNS 搜索列表中。
+[集群层面日志](/zh-cn/docs/concepts/architecture/#cluster-level-logging)
+: 用于将容器日志保存到中央日志存储
 
 <!--
-### Web UI (Dashboard)
-
-[Dashboard](/docs/tasks/access-application-cluster/web-ui-dashboard/) is a general purpose,
-web-based UI for Kubernetes clusters. It allows users to manage and troubleshoot applications
-running in the cluster, as well as the cluster itself.
--->
-### Web 界面（仪表盘）   {#web-ui-dashboard}
-
-[Dashboard](/zh-cn/docs/tasks/access-application-cluster/web-ui-dashboard/)
-是 Kubernetes 集群的通用的、基于 Web 的用户界面。
-它使用户可以管理集群中运行的应用程序以及集群本身，
-并进行故障排除。
+## Flexibility in Architecture
 
-<!--
-### Container Resource Monitoring
+Kubernetes allows for flexibility in how these components are deployed and managed. The architecture can be adapted to various needs, from small development environments to large-scale production deployments.
 
-[Container Resource Monitoring](/docs/tasks/debug/debug-cluster/resource-usage-monitoring/)
-records generic time-series metrics
-about containers in a central database, and provides a UI for browsing that data.
+For more detailed information about each component and various ways to configure your cluster architecture, see the [Cluster Architecture](/docs/concepts/architecture/) page.
 -->
-### 容器资源监控   {#container-resource-monitoring}
-
-[容器资源监控](/zh-cn/docs/tasks/debug/debug-cluster/resource-usage-monitoring/)
-将关于容器的一些常见的时间序列度量值保存到一个集中的数据库中，
-并提供浏览这些数据的界面。
+## 架构灵活性    {#flexibility-in-architecture}
 
-<!--
-### Cluster-level Logging
-
-A [cluster-level logging](/docs/concepts/cluster-administration/logging/) mechanism is responsible for
-saving container logs to a central log store with search/browsing interface.
--->
-### 集群层面日志   {#cluster-level-logging}
+Kubernetes 允许灵活地部署和管理这些组件。此架构可以适应各种需求，从小型开发环境到大规模生产部署。
 
-[集群层面日志](/zh-cn/docs/concepts/cluster-administration/logging/)机制负责将容器的日志数据保存到一个集中的日志存储中，
-这种集中日志存储提供搜索和浏览接口。
-
-<!--
-### Network Plugins
-
-[Network plugins](/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins) are software
-components that implement the container network interface (CNI) specification. They are responsible for
-allocating IP addresses to pods and enabling them to communicate with each other within the cluster.
--->
-### 网络插件   {#network-plugins}
-
-[网络插件](/zh-cn/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins)
-是实现容器网络接口（CNI）规范的软件组件。它们负责为 Pod 分配 IP 地址，并使这些 Pod 能在集群内部相互通信。
-
-## {{% heading "whatsnext" %}}
-
-<!--
-Learn more about the following:
-   * [Nodes](/docs/concepts/architecture/nodes/) and [their communication](/docs/concepts/architecture/control-plane-node-communication/)
-     with the control plane.
-   * Kubernetes [controllers](/docs/concepts/architecture/controller/).
-   * [kube-scheduler](/docs/concepts/scheduling-eviction/kube-scheduler/) which is the default scheduler for Kubernetes.
-   * Etcd's official [documentation](https://etcd.io/docs/).
-   * Several [container runtimes](/docs/setup/production-environment/container-runtimes/) in Kubernetes.
-   * Integrating with cloud providers using [cloud-controller-manager](/docs/concepts/architecture/cloud-controller/).
-   * [kubectl](/docs/reference/generated/kubectl/kubectl-commands) commands.
--->
-进一步了解以下内容：
-   * [节点](/zh-cn/docs/concepts/architecture/nodes/)及其与[控制平面](/zh-cn/docs/concepts/architecture/control-plane-node-communication/)的通信。
-   * Kubernetes 中的[控制器](/zh-cn/docs/concepts/architecture/controller/)。
-   * Kubernetes 的默认调度程序 [kube-scheduler](/zh-cn/docs/concepts/scheduling-eviction/kube-scheduler/)。
-   * etcd 的官方[文档](https://etcd.io/docs/)。
-   * Kubernetes 中的几个[容器运行时](/zh-cn/docs/setup/production-environment/container-runtimes/)。
-   * 使用 [cloud-controller-manager](/zh-cn/docs/concepts/architecture/cloud-controller/) 与云提供商进行集成。
-   * [kubectl](/docs/reference/generated/kubectl/kubectl-commands) 命令。
+有关每个组件的详细信息以及配置集群架构的各种方法，
+请参阅[集群架构](/zh-cn/docs/concepts/architecture/)页面。