Merge pull request #43331 from tengqm/zh-sync-glossary

[zh] Sync glossary entries
2023-10-05 17:20:15 +02:00 · 2023-10-05 17:20:15 +02:00 · 1a32094c4b
parent c069b4df7d d4dcec2f00
commit 1a32094c4b
11 changed files with 48 additions and 39 deletions
--- a/content/zh-cn/docs/reference/glossary/cloud-controller-manager.md
+++ b/content/zh-cn/docs/reference/glossary/cloud-controller-manager.md
@ -29,13 +29,14 @@ tags:

 <!--
 A Kubernetes {{< glossary_tooltip text="control plane" term_id="control-plane" >}} component
-that embeds cloud-specific control logic. The cloud controller manager lets you link your
+that embeds cloud-specific control logic. The [cloud controller manager](/docs/concepts/architecture/cloud-controller/) lets you link your
 cluster into your cloud provider's API, and separates out the components that interact
 with that cloud platform from components that only interact with your cluster.
 -->
 一个 Kubernetes {{<glossary_tooltip text="控制平面" term_id="control-plane" >}}组件，
 嵌入了特定于云平台的控制逻辑。
-云控制器管理器（Cloud Controller Manager）允许你将你的集群连接到云提供商的 API 之上，
+[云控制器管理器（Cloud Controller Manager）](/zh-cn/docs/concepts/architecture/cloud-controller/)
+允许你将你的集群连接到云提供商的 API 之上，
 并将与该云平台交互的组件同与你的集群交互的组件分离开来。

 <!--more-->
--- a/content/zh-cn/docs/reference/glossary/container-runtime-interface.md
+++ b/content/zh-cn/docs/reference/glossary/container-runtime-interface.md
@ -24,9 +24,9 @@ tags:
 -->

 <!--
-The main protocol for the communication between the kubelet and Container Runtime.
+The main protocol for the communication between the {{< glossary_tooltip text="kubelet" term_id="kubelet" >}} and Container Runtime.
 -->
-kubelet 和容器运行时之间通信的主要协议。
+{{< glossary_tooltip text="kubelet" term_id="kubelet" >}} 和容器运行时之间通信的主要协议。

 <!--more-->

--- a/content/zh-cn/docs/reference/glossary/cri.md
+++ b/content/zh-cn/docs/reference/glossary/cri.md
@ -27,13 +27,16 @@ tags:

 <!--
 The container runtime interface (CRI) is an API for container runtimes
-to integrate with kubelet on a node.
+to integrate with {{< glossary_tooltip text="kubelet" term_id="kubelet" >}} on a node.
 -->
-容器运行时接口（Container Runtime Interface；CRI）是一组与节点上 kubelet 集成的容器运行时 API。
+容器运行时接口（Container Runtime Interface；CRI）是一组让容器运行时与节点上
+{{< glossary_tooltip text="kubelet" term_id="kubelet" >}} 集成的 API。

 <!--more-->

 <!--
 For more information, see the [CRI](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-node/container-runtime-interface.md) API and specifications.
 -->
-更多信息， 请参考 [容器运行时接口](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-node/container-runtime-interface.md) API 与规格。
+更多信息，请参考[容器运行时接口（CRI）](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-node/container-runtime-interface.md)
+API 与规范。
+
--- a/content/zh-cn/docs/reference/glossary/dockershim.md
+++ b/content/zh-cn/docs/reference/glossary/dockershim.md
@ -25,10 +25,12 @@ tags:

 <!--
 The dockershim is a component of Kubernetes version 1.23 and earlier. It allows the kubelet
+{{< glossary_tooltip text="kubelet" term_id="kubelet" >}}
 to communicate with {{< glossary_tooltip text="Docker Engine" term_id="docker" >}}.
 -->
 dockershim 是 Kubernetes v1.23 及之前版本中的一个组件。
-Kubernetes 系统组件通过它与 {{< glossary_tooltip text="Docker Engine" term_id="docker" >}}通信。
+这个组件使得 {{< glossary_tooltip text="kubelet" term_id="kubelet" >}}
+能够与 {{< glossary_tooltip text="Docker Engine" term_id="docker" >}} 通信。

 <!--more-->

--- a/content/zh-cn/docs/reference/glossary/event.md
+++ b/content/zh-cn/docs/reference/glossary/event.md
@ -4,7 +4,7 @@ id: event
 date: 2022-01-16
 full_link: /zh-cn/docs/reference/kubernetes-api/cluster-resources/event-v1/
 short_description: >
-   对集群中某处所发生事件的报告。通常用来表述系统中某种状态变更。
+  事件（Event）是描述系统中某些状态变化的 Kubernetes 对象。 
 aka: 
 tags:
 - core-object
@ -16,7 +16,7 @@ id: event
 date: 2022-01-16
 full_link: /docs/reference/kubernetes-api/cluster-resources/event-v1/
 short_description: >
-   A report of an event somewhere in the cluster. It generally denotes some state change in the system.
+   Events are Kubernetes objects that describe some state change in the system.
 aka: 
 tags:
 - core-object
@ -24,11 +24,9 @@ tags:
 -->

 <!--
-Each Event is a report of an event somewhere in the {{< glossary_tooltip text="cluster" term_id="cluster" >}}. 
-It generally denotes some state change in the system.
+Event is a Kubernetes object that describes state change/notable occurrences in the system.
 -->
-每个 Event 是{{< glossary_tooltip text="集群" term_id="cluster" >}}中某处所发生事件的报告。
-它通常用来表述系统中的某种状态变更。
+事件（Event）是描述系统状态变化以及需要注意的事情的 Kubernetes 对象。

 <!--more-->

@ -50,5 +48,6 @@ Events should be treated as informative, best-effort, supplemental data.
 In Kubernetes, [auditing](/docs/tasks/debug/debug-cluster/audit/) generates a different kind of
 Event record (API group `audit.k8s.io`).
 -->
-在 Kubernetes 中，[审计](/zh-cn/docs/tasks/debug/debug-cluster/audit/)
-机制会生成一种不同类别的 Event 记录（API 组为 `audit.k8s.io`）。
+在 Kubernetes 中，
+[审计](/zh-cn/docs/tasks/debug/debug-cluster/audit/)机制会生成一种不同类别的
+Event 记录（API 组为 `audit.k8s.io`）。
--- a/content/zh-cn/docs/reference/glossary/kubelet.md
+++ b/content/zh-cn/docs/reference/glossary/kubelet.md
@ -33,8 +33,12 @@ tags:
 <!--more-->

 <!--
-The kubelet takes a set of PodSpecs that are provided through various mechanisms and ensures that the containers described in those PodSpecs are running and healthy. The kubelet doesn't manage containers which were not created by Kubernetes.
+The [kubelet](/docs/reference/command-line-tools-reference/kubelet/) takes a set of PodSpecs that 
+are provided through various mechanisms and ensures that the containers described in those 
+PodSpecs are running and healthy. The kubelet doesn't manage containers which were not created by 
+Kubernetes.
 -->
-kubelet 接收一组通过各类机制提供给它的 PodSpecs，
-确保这些 PodSpecs 中描述的容器处于运行状态且健康。
+[kubelet](/docs/reference/command-line-tools-reference/kubelet/)
+接收一组通过各类机制提供给它的 PodSpec，确保这些 PodSpec 中描述的容器处于运行状态且健康。
 kubelet 不会管理不是由 Kubernetes 创建的容器。
+
--- a/content/zh-cn/docs/reference/glossary/mirror-pod.md
+++ b/content/zh-cn/docs/reference/glossary/mirror-pod.md
@ -27,11 +27,11 @@ tags:
 A {{< glossary_tooltip text="pod" term_id="pod" >}} object that a kubelet uses
 to represent a {{< glossary_tooltip text="static pod" term_id="static-pod" >}}
 -->
-镜像 Pod（Mirror Pod）是被 kubelet 用来代表{{< glossary_tooltip text="静态 Pod" term_id="static-pod" >}} 的
-{{< glossary_tooltip text="pod" term_id="pod" >}} 对象。
+镜像 Pod（Mirror Pod）是被 {{< glossary_tooltip text="kubelet" term_id="kubelet" >}}
+用来代表{{< glossary_tooltip text="静态 Pod" term_id="static-pod" >}} 的
+{{< glossary_tooltip text="Pod" term_id="pod" >}} 对象。

 <!--more-->
-<!--更多-->

 <!--
 When the kubelet finds a static pod in its configuration, it automatically tries to
@ -44,4 +44,4 @@ will be visible on the API server, but cannot be controlled from there.
 它会自动地尝试在 Kubernetes API 服务器上为它创建 Pod 对象。
 这意味着 pod 在 API 服务器上将是可见的，但不能在其上进行控制。

-（例如，删除镜像 Pod 也不会阻止 kubelet 守护进程继续运行它）。
+（例如，删除镜像 Pod 也不会阻止 kubelet 守护进程继续运行它）。
--- a/content/zh-cn/docs/reference/glossary/object.md
+++ b/content/zh-cn/docs/reference/glossary/object.md
@ -15,7 +15,7 @@ id: object
 date: 2020-10-12
 full_link: /docs/concepts/overview/working-with-objects/#kubernetes-objects
 short_description: >
-   A entity in the Kubernetes system, representing part of the state of your cluster.
+   An entity in the Kubernetes system, representing part of the state of your cluster.
 aka: 
 tags:
 - fundamental
@ -35,7 +35,8 @@ that the item it represents actually exists.
 By creating an object, you're effectively telling the Kubernetes system what you want that part of
 your cluster's workload to look like; this is your cluster's desired state.
 -->
-Kubernetes 对象通常是一个“目标记录”-一旦你创建了一个对象，Kubernetes 
-{{< glossary_tooltip text="控制平面（Control Plane）" term_id="control-plane" >}} 
-不断工作，以确保它代表的项目确实存在。
-创建一个对象相当于告知 Kubernetes 系统：你期望这部分集群负载看起来像什么；这也就是你集群的期望状态。
+Kubernetes 对象通常是一个“意向表述（Record of Intent）”—一旦你创建了一个对象，Kubernetes 
+{{< glossary_tooltip text="控制平面（Control Plane）" term_id="control-plane" >}} 就不断工作，
+以确保它所代表的事物确实存在。
+创建一个对象相当于告知 Kubernetes 系统：你期望这部分集群负载看起来像什么；这也就是你集群的期望状态。
+
--- a/content/zh-cn/docs/reference/glossary/probe.md
+++ b/content/zh-cn/docs/reference/glossary/probe.md
@ -24,10 +24,11 @@ tags:
 -->

 <!--
-A check that the kubelet periodically performs against a container that is 
+A check that the {{< glossary_tooltip text="kubelet" term_id="kubelet" >}} periodically performs against a container that is 
 running in a pod, that will define container's state and health and informing container's lifecycle.
 -->
-由 kubelet 定期对运行在 Pod 中的容器执行的一项检查，用于定义容器的状态和健康状况，并通知容器的生命周期。
+由 {{< glossary_tooltip text="kubelet" term_id="kubelet" >}} 定期对运行在 Pod 中的容器执行的一项检查，
+用于定义容器的状态和健康状况，并通知容器的生命周期。

 <!--more-->

--- a/content/zh-cn/docs/reference/glossary/static-pod.md
+++ b/content/zh-cn/docs/reference/glossary/static-pod.md
@ -25,18 +25,16 @@ tags:
 -->

 <!--
-A {{< glossary_tooltip text="pod" term_id="pod" >}} managed directly by the kubelet
+A {{< glossary_tooltip text="pod" term_id="pod" >}} managed directly by the {{< glossary_tooltip text="kubelet" term_id="kubelet" >}}
 daemon on a specific node,
-->
-由特定节点上的 kubelet 守护进程直接管理的 {{< glossary_tooltip text="Pod" term_id="pod" >}}，
-<!--more-->
-
-<!--
 without the API server observing it.
 -->
+由特定节点上的 {{< glossary_tooltip text="kubelet" term_id="kubelet" >}} 守护进程直接管理的
+{{< glossary_tooltip text="Pod" term_id="pod" >}}。
 API 服务器不了解它的存在。

 <!--
 Static Pods do not support {{< glossary_tooltip text="ephemeral containers" term_id="ephemeral-container" >}}.
 -->
 静态 Pod 不支持{{< glossary_tooltip text="临时容器" term_id="ephemeral-container" >}}。
+
--- a/content/zh-cn/docs/reference/glossary/workload.md
+++ b/content/zh-cn/docs/reference/glossary/workload.md
@ -1,6 +1,6 @@
 ---
 title: 工作负载（Workload）
-id: workloads
+id: workload
 date: 2019-02-13
 full_link: /zh-cn/docs/concepts/workloads/
 short_description: >
@ -12,7 +12,7 @@ tags:
 ---
 <!-- 
 title: Workload
-id: workloads
+id: workload
 date: 2019-02-13
 full_link: /docs/concepts/workloads/
 short_description: >
@ -42,4 +42,4 @@ in a {{< glossary_tooltip term_id="Deployment" >}}.

 例如，具有 Web 服务器和数据库的工作负载可能在一个
 {{< glossary_tooltip term_id="StatefulSet" >}} 中运行数据库，
-而 Web 服务器运行在 {{< glossary_tooltip term_id="Deployment" >}}。
+而 Web 服务器运行在 {{< glossary_tooltip term_id="Deployment" >}}。