Merge pull request #53357 from windsonsea/gloh2p

[zh] Sync glossary from h to n

Author: k8s-ci-robot

content/zh-cn/docs/reference/glossary/helm-chart.md

@@ -4,7 +4,7 @@ id: helm-chart
 date: 2018-04-12
 full_link: https://helm.sh/docs/topics/charts/
 short_description: >
-  Helm Chart 是一组预先配置的 Kubernetes 资源所构成的包，可以使用 Helm 工具对其进行管理。
+  Helm Chart 是一组预先定义的 Kubernetes 配置所构成的包，可以使用 Helm 工具对其进行管理。
 
 aka: 
 tags:
@@ -16,19 +16,19 @@ id: helm-chart
 date: 2018-04-12
 full_link: https://helm.sh/docs/topics/charts/
 short_description: >
-  A package of pre-configured Kubernetes resources that can be managed with the Helm tool.
+  A package of pre-configured Kubernetes configurations that can be managed with the Helm tool.
 
 aka: 
 tags:
 - tool
 -->
 
 <!--
- A package of pre-configured Kubernetes resources that can be managed with the Helm tool.
+A package of pre-configured Kubernetes configurations that can be managed with the Helm tool.
 -->
-Helm Chart 是一组预先配置的 Kubernetes 资源所构成的包，可以使用 Helm 工具对其进行管理。
+Helm Chart 是一组预先定义的 Kubernetes 配置所构成的包，可以使用 Helm 工具对其进行管理。
 
-<!--more--> 
+<!--more-->
 
 <!--
 Charts provide a reproducible way of creating and sharing Kubernetes applications.

content/zh-cn/docs/reference/glossary/horizontal-pod-autoscaler.md

@@ -1,10 +1,10 @@
 ---
-title: Pod 水平自动扩缩器（Horizontal Pod Autoscaler）
+title: Pod 水平自动扩缩器
 id: horizontal-pod-autoscaler
 date: 2018-04-12
 full_link: /zh-cn/docs/tasks/run-application/horizontal-pod-autoscale/
 short_description: >
-  Pod 水平自动扩缩器（Horizontal Pod Autoscaler）是一种 API 资源，它根据目标 CPU 利用率或自定义度量目标扩缩 Pod 副本的数量。
+  此对象根据目标资源利用率或自定义度量目标自动扩缩 Pod 副本的数量。
 
 aka: 
 - HPA
@@ -17,7 +17,7 @@ id: horizontal-pod-autoscaler
 date: 2018-04-12
 full_link: /docs/tasks/run-application/horizontal-pod-autoscale/
 short_description: >
-  An API resource that automatically scales the number of pod replicas based on targeted CPU utilization or custom metric targets.
+  Object that automatically scales the number of pod replicas based on targeted resource utilization or custom metric targets.
 
 aka: 
 - HPA
@@ -26,16 +26,18 @@ tags:
 -->
 
 <!--
- An API resource that automatically scales the number of {{< glossary_tooltip term_id="pod" >}} replicas based on targeted CPU utilization or custom metric targets.
+An {{< glossary_tooltip text="object" term_id="object" >}} that automatically scales the number of {{< glossary_tooltip term_id="pod" >}} replicas,
+based on targeted {{< glossary_tooltip text="resource" term_id="infrastructure-resource" >}} utilization or custom metric targets.
 -->
-Pod 水平自动扩缩器（Horizontal Pod Autoscaler）是一种 API 资源，它根据目标 CPU 利用率或自定义度量目标扩缩 {{< glossary_tooltip term_id="pod" >}} 副本的数量。
+此{{< glossary_tooltip text="对象" term_id="object" >}}根据目标{{< glossary_tooltip text="资源" term_id="infrastructure-resource" >}}利用率或自定义度量目标自动扩缩
+{{< glossary_tooltip term_id="pod" >}} 副本的数量。
 
 <!--more--> 
 
 <!--
-HPA is typically used with {{< glossary_tooltip text="ReplicationControllers" term_id="replication-controller" >}}, {{< glossary_tooltip text="Deployments" term_id="deployment" >}}, or {{< glossary_tooltip text="ReplicaSets" term_id="replica-set" >}}. It cannot be applied to objects that cannot be scaled, for example {{< glossary_tooltip text="DaemonSets" term_id="daemonset" >}}.
+HorizontalPodAutoscaler (HPA) is typically used with {{< glossary_tooltip text="Deployments" term_id="deployment" >}}, or {{< glossary_tooltip text="ReplicaSets" term_id="replica-set" >}}. It cannot be applied to objects that cannot be scaled, for example {{< glossary_tooltip text="DaemonSets" term_id="daemonset" >}}.
 -->
-HPA 通常用于 {{< glossary_tooltip text="ReplicationController" term_id="replication-controller" >}}
-、{{< glossary_tooltip text="Deployment" term_id="deployment" >}} 
+HorizontalPodAutoscaler (HPA) 通常用于
+{{< glossary_tooltip text="Deployment" term_id="deployment" >}} 
 或者 {{< glossary_tooltip text="ReplicaSet" term_id="replica-set" >}} 上。
-HPA 不能用于不支持扩缩的对象，例如 {{< glossary_tooltip text="DaemonSets" term_id="daemonset" >}}。
+HPA 不能用于不支持扩缩的对象，例如 {{< glossary_tooltip text="DaemonSet" term_id="daemonset" >}}。

content/zh-cn/docs/reference/glossary/kube-scheduler.md

@@ -11,9 +11,7 @@ tags:
 - architecture
 - scheduler
 ---
-
 <!--
----
 title: kube-scheduler
 id: kube-scheduler
 date: 2018-04-12
@@ -24,24 +22,27 @@ short_description: >
 aka: 
 tags:
 - architecture
----
 -->
 
 <!--
 Control plane component that watches for newly created
 {{< glossary_tooltip term_id="pod" text="Pods" >}} with no assigned
 {{< glossary_tooltip term_id="node" text="node">}}, and selects a node for them
-to run on.-->
-
-  `kube-scheduler` 是{{< glossary_tooltip text="控制平面" term_id="control-plane" >}}的组件，
-  负责监视新创建的、未指定运行{{< glossary_tooltip term_id="node" text="节点（node）">}}的 {{< glossary_tooltip term_id="pod" text="Pods" >}}，
-  并选择节点来让 Pod 在上面运行。
+to run on.
+-->
+`kube-scheduler` 是{{< glossary_tooltip text="控制平面" term_id="control-plane" >}}的组件，
+负责监视新创建的、未指定运行{{< glossary_tooltip term_id="node" text="节点">}}的
+{{< glossary_tooltip term_id="pod" text="Pod" >}}，
+并选择节点来让 Pod 在上面运行。
 
-<!--more--> 
+<!--more-->
 
 <!--
-Factors taken into account for scheduling decisions include individual and collective resource requirements,  hardware/software/policy constraints, affinity and anti-affinity specifications, data locality, inter-workload interference and deadlines.
+Factors taken into account for scheduling decisions include:
+individual and collective {{< glossary_tooltip text="resource" term_id="infrastructure-resource" >}}
+requirements, hardware/software/policy constraints, affinity and anti-affinity specifications,
+data locality, inter-workload interference, and deadlines.
 -->
-
-调度决策考虑的因素包括单个 Pod 及 Pods 集合的资源需求、软硬件及策略约束、
-亲和性及反亲和性规范、数据位置、工作负载间的干扰及最后时限。
+调度决策考虑的因素包括单个 Pod 及多个 Pod
+集合的{{< glossary_tooltip text="资源" term_id="infrastructure-resource" >}}需求、
+软硬件及策略约束、亲和性及反亲和性规范、数据位置、工作负载间的干扰及最后时限。

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

@@ -10,32 +10,29 @@ aka:
 tags:
 - fundamental
 ---
-
 <!--
----
 title: Name
 id: name
 date: 2018-04-12
-full_link: /docs/concepts/overview/working-with-objects/names/
+full_link: /docs/concepts/overview/working-with-objects/names
 short_description: >
   A client-provided string that refers to an object in a resource URL, such as `/api/v1/pods/some-name`.
 
 aka: 
 tags:
 - fundamental
----
 -->
 
 <!--
- A client-provided string that refers to an object in a resource URL, such as `/api/v1/pods/some-name`.
+A client-provided string that refers to an object in a {{< glossary_tooltip text="resource" term_id="api-resource" >}}
+URL, such as `/api/v1/pods/some-name`.
 -->
+客户端提供的字符串，引用{{< glossary_tooltip text="资源" term_id="api-resource" >}} URL
+中的对象，如 `/api/v1/pods/some-name`。
 
-客户端提供的字符串，引用资源 URL 中的对象，如`/api/v1/pods/some name`。
-
-<!--more--> 
+<!--more-->
 
 <!--
 Only one object of a given kind can have a given name at a time. However, if you delete the object, you can make a new object with the same name.
 -->
-
 某一时刻，只能有一个给定类型的对象具有给定的名称。但是，如果删除该对象，则可以创建同名的新对象。

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

@@ -10,36 +10,33 @@ aka:
 tags:
 - fundamental
 ---
-
 <!--
----
 title: Namespace
 id: namespace
 date: 2018-04-12
-full_link: /docs/concepts/overview/working-with-objects/namespaces/
+full_link: /docs/concepts/overview/working-with-objects/namespaces
 short_description: >
   An abstraction used by Kubernetes to support isolation of groups of resources within a single cluster.
 
 aka: 
 tags:
 - fundamental
----
 -->
 
 <!--
- An abstraction used by Kubernetes to support isolation of groups of resources within a single {{< glossary_tooltip text="cluster" term_id="cluster" >}}.
+An abstraction used by Kubernetes to support isolation of groups of {{< glossary_tooltip text="API resources" term_id="api-resource" >}}
+within a single {{< glossary_tooltip text="cluster" term_id="cluster" >}}.
 -->
+名字空间是 Kubernetes 用来支持隔离单个{{< glossary_tooltip text="集群" term_id="cluster" >}}中的
+{{< glossary_tooltip text="API 资源" term_id="api-resource" >}}组的一种抽象。
 
-名字空间是 Kubernetes 用来支持隔离单个 {{< glossary_tooltip text="集群" term_id="cluster" >}}中的资源组的一种抽象。
-
-<!--more--> 
+<!--more-->
 
 <!--
-Namespaces are used to organize objects in a cluster and provide a way to divide cluster resources. Names of resources need to be unique within a namespace, but not across namespaces. Namespace-based scoping is applicable only for namespaced objects _(e.g. Deployments, Services, etc)_ and not for cluster-wide objects _(e.g. StorageClass, Nodes, PersistentVolumes, etc)_.
+Namespaces are used to organize objects in a cluster and provide a way to divide cluster resources. Names of resources need to be unique within a namespace, but not across namespaces. Namespace-based scoping is applicable only for namespaced resources _(for example: Pods, Deployments, Services)_ and not for cluster-wide resources _(for example: StorageClasses, Nodes, PersistentVolumes)_.
 -->
-
 名字空间用来组织集群中对象，并为集群资源划分提供了一种方法。
 同一名字空间内的资源名称必须唯一，但跨名字空间时不作要求。
-基于名字空间的作用域限定仅适用于名字空间作用域的对象（例如 Deployment、Services 等），
+基于名字空间的作用域限定仅适用于名字空间作用域的对象（例如 Pod、Deployment、Service 等），
 而不适用于集群作用域的对象（例如 StorageClass、Node、PersistentVolume 等）。
 在一些文档里名字空间也称为命名空间。

content/zh-cn/docs/reference/glossary/network-policy.md

@@ -13,9 +13,7 @@ tags:
 - extension
 - core-object
 ---
-
 <!--
----
 title: Network Policy
 id: network-policy
 date: 2018-04-12
@@ -29,16 +27,14 @@ tags:
 - architecture
 - extension
 - core-object
----
 -->
 
 <!--
 A specification of how groups of Pods are allowed to communicate with each other and with other network endpoints.
 -->
-
 网络策略是一种规范，规定了允许 Pod 组之间、Pod 与其他网络端点之间以怎样的方式进行通信。
 
-<!--more--> 
+<!--more-->
 
 <!--
 NetworkPolicies help you declaratively configure which Pods are allowed to connect to each other, which namespaces are allowed to communicate,
@@ -48,7 +44,6 @@ to select Pods and define rules which specify what traffic is allowed to the sel
 NetworkPolicies are implemented by a supported network plugin provided by a network provider.
 Be aware that creating a NetworkPolicy object without a controller to implement it will have no effect.
 -->
-
 网络策略帮助你声明式地配置允许哪些 Pod 之间、哪些命名空间之间允许进行通信，
 并具体配置了哪些端口号来执行各个策略。`NetworkPolicy`
 资源使用{{< glossary_tooltip text="标签" term_id="label" >}}来选择 Pod，

content/zh-cn/docs/reference/glossary/node-pressure-eviction.md

@@ -11,20 +11,17 @@ tags:
 - operation
 ---
 <!-- 
----
 title: Node-pressure eviction
 id: node-pressure-eviction
 date: 2021-05-13
 full_link: /docs/concepts/scheduling-eviction/node-pressure-eviction/
 short_description: >
   Node-pressure eviction is the process by which the kubelet proactively fails
-  pods to reclaim {{< glossary_tooltip text="resource" term_id="infrastructure-resource" >}}
-  on nodes.
+  pods to reclaim resources on nodes.
 aka:
 - kubelet eviction
 tags:
 - operation
----
 -->
 
 <!-- 
@@ -48,4 +45,4 @@ kubelet 可以主动使节点上的一个或多个 Pod 失效，以回收资源
 <!-- 
 Node-pressure eviction is not the same as [API-initiated eviction](/docs/concepts/scheduling-eviction/api-eviction/).
 -->
-节点压力驱逐不用于 [API 发起的驱逐](/zh-cn/docs/concepts/scheduling-eviction/api-eviction/)。
+节点压力驱逐不同于 [API 发起的驱逐](/zh-cn/docs/concepts/scheduling-eviction/api-eviction/)。