[zh] Sync glossary from c to e

Author: windsonsea

content/zh-cn/docs/reference/glossary/customresourcedefinition.md

@@ -26,16 +26,19 @@ tags:
 - operation
 - extension
 -->
- 
+
 <!--
- Custom code that defines a resource to add to your Kubernetes API server without building a complete custom server.
+A kind of {{< glossary_tooltip text="API object" term_id="object" >}} that defines a new custom API to add
+to your Kubernetes API server, without building a complete custom server.
 -->
- 通过定制化的代码给你的 Kubernetes API 服务器增加资源对象，而无需编译完整的定制 API 服务器。
+一种 {{< glossary_tooltip text="API 对象" term_id="object" >}}，
+用于定义一个新的定制 API 添加到你的 Kubernetes API 服务器，无需构建一个完整的定制服务器。
 
-<!--more--> 
+<!--more-->
 
 <!--
-Custom Resource Definitions let you extend the Kubernetes API for your environment if the publicly supported API resources can't meet your needs. 
+CustomResourceDefinitions let you extend the Kubernetes API for your environment if the built-in
+{{< glossary_tooltip text="API resources" term_id="api-resource" >}} can't meet your needs.
 -->
-当 Kubernetes 公开支持的 API 资源不能满足你的需要时，
-定制资源对象（Custom Resource Definitions）让你可以在你的环境上扩展 Kubernetes API。
+当内置的 {{< glossary_tooltip text="API 资源" term_id="api-resource" >}}不能满足你的需要时，
+定制资源对象（CustomResourceDefinition）让你可以在你的环境上扩展 Kubernetes API。

content/zh-cn/docs/reference/glossary/device-plugin.md

@@ -34,7 +34,7 @@ steps.
 设备插件在工作{{<glossary_tooltip term_id="node" text="节点">}}上运行并为
 {{<glossary_tooltip term_id="pod" text="Pod">}}
 提供访问基础设施{{< glossary_tooltip text="资源" term_id="infrastructure-resource" >}}的能力，
-例如：本地硬件这类资源需要特定于供应商的初始化或安装步骤。
+例如本地硬件这类资源需要特定于供应商的初始化或安装步骤。
 
 <!--more-->
 
@@ -45,14 +45,13 @@ Pods can access hardware features that relate to the Node where that Pod is runn
 You can deploy a device plugin as a {{< glossary_tooltip term_id="daemonset" >}},
 or install the device plugin software directly on each target Node.
 -->
-设备插件向 {{<glossary_tooltip term_id="kubelet" text="kubelet" >}} 公布资源，以便工作负载
-Pod 访问 Pod 运行所在节点上的硬件功能特性。
+设备插件向 {{<glossary_tooltip term_id="kubelet" text="kubelet" >}}
+公布资源，以便工作负载 Pod 访问 Pod 运行所在节点上的硬件功能特性。
 你可以将设备插件部署为 {{<glossary_tooltip term_id="daemonset" >}}，
 或者直接在每个目标节点上安装设备插件软件。
 
 <!-- 
 See
-	 
 [Device Plugins](/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/)
 for more information.
 -->

content/zh-cn/docs/reference/glossary/endpoint-slice.md

@@ -4,7 +4,7 @@ id: endpoint-slice
 date: 2018-04-12
 full_link: /zh-cn/docs/concepts/services-networking/endpoint-slices/
 short_description: >
-  EndpointSlices 跟踪具有匹配 Service 选择算符的 Pod 的 IP 地址。
+  EndpointSlices 跟踪提供 Service 的 Pod 的 IP 地址。
 
 aka:
 tags:
@@ -16,23 +16,37 @@ id: endpoint-slice
 date: 2018-04-12
 full_link: /docs/concepts/services-networking/endpoint-slices/
 short_description: >
-  EndpointSlices track the IP addresses of Pods with matching Service selectors.
+  EndpointSlices track the IP addresses of Pods for Services.
 
 aka:
 tags:
 - networking
 -->
 
 <!--
- EndpointSlices track the IP addresses of Pods with matching  {{< glossary_tooltip text="selectors" term_id="selector" >}}.
+EndpointSlices track the IP addresses of backend endpoints.
+EndpointSlices are normally associated with a
+{{< glossary_tooltip text="Service" term_id="service" >}} and the backend endpoints typically represent
+{{< glossary_tooltip text="Pods" term_id="pod" >}}.
 -->
-EndpointSlices 跟踪具有匹配{{< glossary_tooltip text="选择算符" term_id="selector" >}}的
-Pod 的 IP 地址。
+EndpointSlices 跟踪后端端点的 IP 地址。
+EndpointSlices 通常与某个 {{< glossary_tooltip text="Service" term_id="service" >}} 关联，
+后端端点通常表示 {{< glossary_tooltip text="Pod" term_id="pod" >}}。
 
 <!--more-->
 
 <!--
-EndpointSlices can be configured manually for {{< glossary_tooltip text="Services" term_id="service" >}} without selectors specified.
+One Service can be backed by multiple Pods. Kubernetes represents the backing endpoints of a Service
+with a set of EndpointSlices that are associated with that Service.
+The backing endpoints are usually, but not always, pods running in the cluster.
+
+The control plane usually manages EndpointSlices for you automatically. However,
+EndpointSlices can be defined manually for {{< glossary_tooltip text="Services" term_id="service" >}} without
+{{< glossary_tooltip text="selectors" term_id="selector" >}} specified.
 -->
-EndpointSlices 可以手动配置给没有指定选择算符的
+一个 Service 可以由多个 Pod 支撑。Kubernetes 使用与该 Service 关联的一组 EndpointSlice
+来表示这些支撑 Service 的端点。这些支撑的端点通常是集群中运行的 Pod，但并非总是如此。
+
+控制平面通常为你自动管理 EndpointSlice。
+EndpointSlice 可以手动定义给没有指定{{< glossary_tooltip text="选择算符" term_id="selector" >}}的
 {{< glossary_tooltip text="Service" term_id="service" >}}。

content/zh-cn/docs/reference/glossary/endpoint.md

@@ -2,49 +2,43 @@
 title: 端点（Endpoints）
 id: endpoints
 date: 2020-04-23
-full_link: 
+full_link: /zh-cn/docs/concepts/services-networking/service/#endpoints
 short_description: >
-  Service 的一个端点是实现该服务的 Pod 之一（或外部服务器）。
-
-aka:
+  表示 Service 端点的 API（已弃用）
 tags:
 - networking
 ---
 <!--
 title: Endpoints
 id: endpoints
 date: 2020-04-23
-full_link: 
+full_link: /docs/concepts/services-networking/service/#endpoints
 short_description: >
-  An endpoint of a Service is one of the Pods (or external servers) that implements the Service.
-
-aka:
+  (Deprecated) API representing endpoints of a Service
 tags:
 - networking
 -->
 
 <!--
- An endpoint of a {{< glossary_tooltip text="Service" term_id="service" >}} is one of the {{< glossary_tooltip text="Pods" term_id="pod" >}} (or external servers) that implements the Service.
+A deprecated API that represents the set of all endpoints for a
+{{< glossary_tooltip text="Service" term_id="service" >}}.
 -->
-一个 {{< glossary_tooltip text="Service" term_id="service" >}}
-的端点是实现该 Service 的 {{< glossary_tooltip text="Pod 之一" term_id="pod" >}}
-（或外部服务器）。
+一个已弃用的 API，表示某个 {{< glossary_tooltip text="Service" term_id="service" >}}
+的全部端点的集合。
 
 <!--more-->
 
 <!--
-For Services with {{< glossary_tooltip text="selectors" term_id="selector" >}},
-the EndpointSlice controller will automatically create one or more {{<
-glossary_tooltip text="EndpointSlices" term_id="endpoint-slice" >}} giving the
-IP addresses of the selected endpoint Pods.
--->
-对于带有{{< glossary_tooltip text="选择器" term_id="selector" >}}的 Service，
-EndpointSlice 控制器将自动创建一个或多个
-{{< glossary_tooltip text="EndpointSlices" term_id="endpoint-slice" >}}，
-提供选定端点 Pod 的 IP 地址。
+Since v1.21, Kubernetes uses 
+{{< glossary_tooltip text="EndpointSlices" term_id="endpoint-slice" >}}
+rather than Endpoints; the original Endpoints API was deprecated due to
+concerns about scalability.
 
-<!--
-EndpointSlices can also be created manually to indicate the endpoints of
-Services that have no selector specified.
+To learn more about Endpoints, read [Endpoints](/docs/concepts/services-networking/service/#endpoints).
 -->
-EndpointSlices 也可以手动创建，以指示没有指定选择器的服务的端点。
+从 v1.21 起，Kubernetes 使用
+{{< glossary_tooltip text="EndpointSlices" term_id="endpoint-slice" >}}
+来替代 Endpoints；原始的 Endpoints API 因可扩展性方面的考量而被弃用。
+
+有关 Endpoints 的信息，参阅
+[Endpoints](/zh-cn/docs/concepts/services-networking/service/#endpoints)。

content/zh-cn/docs/reference/glossary/ephemeral-container.md

@@ -30,11 +30,14 @@ A {{< glossary_tooltip term_id="container" >}} type that you can temporarily run
 <!--more-->
 
 <!--
-If you want to investigate a Pod that's running with problems, you can add an ephemeral container to that Pod and carry out diagnostics. Ephemeral containers have no resource or scheduling guarantees, and you should not use them to run any part of the workload itself.
+If you want to investigate a Pod that's running with problems, you can add an ephemeral container to that Pod and carry out diagnostics.
+Ephemeral containers have no {{< glossary_tooltip text="resource" term_id="infrastructure-resource" >}} or scheduling guarantees,
+and you should not use them to run any part of the workload itself.
 
 Ephemeral containers are not supported by {{< glossary_tooltip text="static pods" term_id="static-pod" >}}.
 -->
 如果想要调查运行中有问题的 Pod，可以向该 Pod 添加一个临时容器（Ephemeral Container）并进行诊断。
-临时容器没有资源或调度保证，因此不应该使用它们来运行工作负载本身的任何部分。
+临时容器没有{{< glossary_tooltip text="资源" term_id="infrastructure-resource" >}}或调度保证，
+因此不应该使用它们来运行工作负载本身的任何部分。
 
 {{< glossary_tooltip text="静态 Pod" term_id="static-pod" >}} 不支持临时容器。