Merge pull request #25843 from jialaijun/update_glossary

k8s-ci-robot · web-flow · commit e2a9a56b3e88 · 2021-01-06T00:01:51.000-08:00
update the markdown file in the glossary directory for Chinese version.
diff --git a/content/zh/docs/reference/glossary/kube-scheduler.md b/content/zh/docs/reference/glossary/kube-scheduler.md
@@ -4,7 +4,7 @@ id: kube-scheduler
 date: 2018-04-12
 full_link: /docs/reference/generated/kube-scheduler/
 short_description: >
-  主节点上的组件，该组件监视那些新创建的未指定运行节点的 Pod，并选择节点让 Pod 在上面运行。
+  控制平面组件，负责监视新创建的、未指定运行节点的 Pod，选择节点让 Pod 在上面运行。
 
 aka: 
 tags:
@@ -19,7 +19,7 @@ id: kube-scheduler
 date: 2018-04-12
 full_link: /docs/reference/generated/kube-scheduler/
 short_description: >
-  Component on the master that watches newly created pods that have no node assigned, and selects a node for them to run on.
+  Control plane component that watches for newly created pods with no assigned node, and selects a node for them to run on.
 
 aka: 
 tags:
@@ -28,10 +28,12 @@ tags:
 -->
 
 <!--
- Component on the master that watches newly created pods that have no node assigned, and selects a node for them to run on.
--->
+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.-->
 
-主节点上的组件，该组件监视那些新创建的未指定运行节点的 Pod，并选择节点让 Pod 在上面运行。
+  控制平面组件，负责监视新创建的、未指定运行{{< glossary_tooltip term_id="node" text="节点（node）">}}的 {{< glossary_tooltip term_id="pod" text="Pods" >}}，选择节点让 Pod 在上面运行。
 
 <!--more--> 
 
diff --git a/content/zh/docs/reference/glossary/kubelet.md b/content/zh/docs/reference/glossary/kubelet.md
@@ -28,13 +28,14 @@ tags:
 <!--
  An agent that runs on each {{< glossary_tooltip text="node" term_id="node" >}} in the cluster. It makes sure that {{< glossary_tooltip text="containers" term_id="container" >}} are running in a {{< glossary_tooltip text="Pod" term_id="pod" >}}.
 -->
-一个在集群中每个节点上运行的代理。
-它保证容器都运行在 Pod 中。
+一个在集群中每个{{< glossary_tooltip text="节点（node）" term_id="node" >}}上运行的代理。
+它保证{{< glossary_tooltip text="容器（containers）" term_id="container" >}}都
+运行在 {{< glossary_tooltip text="Pod" term_id="pod" >}} 中。
 
 <!--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 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
 中描述的容器处于运行状态且健康。
diff --git a/content/zh/docs/reference/glossary/kubernetes-api.md b/content/zh/docs/reference/glossary/kubernetes-api.md
@@ -17,7 +17,7 @@ tags:
 title: Kubernetes API
 id: kubernetes-api
 date: 2018-04-12
-full_link: /zh/docs/concepts/overview/kubernetes-api/
+full_link: /docs/concepts/overview/kubernetes-api/
 short_description: >
   The application that serves Kubernetes functionality through a RESTful interface and stores the state of the cluster.
 
@@ -40,7 +40,7 @@ Kubernetes API 是通过 RESTful 接口提供 Kubernetes 功能服务并负责
 Kubernetes resources and "records of intent" are all stored as API objects, and modified via RESTful calls to the API. The API allows configuration to be managed in a declarative way. Users can interact with the Kubernetes API directly, or via tools like `kubectl`. The core Kubernetes API is flexible and can also be extended to support custom resources.
 -->
 
-Kubernetes 资源和"意向记录"都是作为 API 对象储存的，并可以通过对 API 的 RESTful 调用进行修改。
+Kubernetes 资源和"意向记录"都是作为 API 对象储存的，并可以通过调用 RESTful 风格的 API 进行修改。
 API 允许以声明方式管理配置。
 用户可以直接和 Kubernetes API 交互，也可以通过 `kubectl` 这样的工具进行交互。
 核心的 Kubernetes API 是很灵活的，可以扩展以支持定制资源。
diff --git a/content/zh/docs/reference/glossary/label.md b/content/zh/docs/reference/glossary/label.md
@@ -1,5 +1,5 @@
 ---
-title: 标签
+title: 标签（Label）
 id: label
 date: 2018-04-12
 full_link: /zh/docs/concepts/overview/working-with-objects/labels/
@@ -15,7 +15,7 @@ tags:
 title: Label
 id: label
 date: 2018-04-12
-full_link: /zh/docs/concepts/overview/working-with-objects/labels/
+full_link: /docs/concepts/overview/working-with-objects/labels/
 short_description: >
   Tags objects with identifying attributes that are meaningful and relevant to users.
 
diff --git a/content/zh/docs/reference/glossary/limitrange.md b/content/zh/docs/reference/glossary/limitrange.md
@@ -41,11 +41,11 @@ related:
 <!--
  Provides constraints to limit resource consumption per {{< glossary_tooltip text="Containers" term_id="container" >}} or {{< glossary_tooltip text="Pods" term_id="pod" >}} in a namespace.
 -->
- 提供约束来限制命名空间中每个 {{< glossary_tooltip text="容器" term_id="container" >}} 或 {{< glossary_tooltip text="Pod" term_id="pod" >}} 的资源消耗。
+ 提供约束来限制命名空间中每个 {{< glossary_tooltip text="容器（Containers）" term_id="container" >}} 或 {{< glossary_tooltip text="Pod" term_id="pod" >}} 的资源消耗。
 
 <!--more--> 
 <!--
 LimitRange limits the quantity of objects that can be created  by type, 
 as well as the amount of compute resources that may be requested/consumed by individual {{< glossary_tooltip text="Containers" term_id="container" >}} or {{< glossary_tooltip text="Pods" term_id="pod" >}} in a namespace.
 -->
-LimitRange 按照类型来限制命名空间中对象能够创建的数量，以及单个 {{< glossary_tooltip text="容器" term_id="container" >}} 或 {{< glossary_tooltip text="Pod" term_id="pod" >}} 可以请求/使用的计算资源量。
+LimitRange 按照类型来限制命名空间中对象能够创建的数量，以及单个 {{< glossary_tooltip text="容器（Containers）" term_id="container" >}} 或 {{< glossary_tooltip text="Pod" term_id="pod" >}} 可以请求/使用的计算资源量。
diff --git a/content/zh/docs/reference/glossary/logging.md b/content/zh/docs/reference/glossary/logging.md
@@ -1,5 +1,5 @@
 ---
-title: 日志
+title: 日志（Logging）
 id: logging
 date: 2019-04-04
 full_link: /zh/docs/concepts/cluster-administration/logging/
@@ -11,7 +11,7 @@ tags:
 - architecture
 - fundamental
 ---
-  日志是 {{< glossary_tooltip text="集群" term_id="cluster" >}} 或应用程序记录的事件列表。
+  日志是 {{< glossary_tooltip text="集群（cluster）" term_id="cluster" >}} 或应用程序记录的事件列表。
   
 <!--
 ---
diff --git a/content/zh/docs/reference/glossary/managed-service.md b/content/zh/docs/reference/glossary/managed-service.md
@@ -32,11 +32,15 @@ tags:
 <!--more--> 
 
 <!--
-Some examples of Managed Services are AWS EC2, Azure SQL Database, and GCP Pub/Sub, but they can be any software offering that can be used by an application. [Service Catalog](/docs/concepts/service-catalog/) provides a way to list, provision, and bind with Managed Services offered by {{< glossary_tooltip text="Service Brokers" term_id="service-broker" >}}.
+Some examples of Managed Services are AWS EC2, Azure SQL Database, and
+GCP Pub/Sub, but they can be any software offering that can be used by an application.
+[Service Catalog](/docs/concepts/extend-kubernetes/service-catalog/) provides a way to
+list, provision, and bind with Managed Services offered by
+{{< glossary_tooltip text="Service Brokers" term_id="service-broker" >}}.
 -->
 托管服务的一些例子有 AWS EC2、Azure SQL 数据库和 GCP Pub/Sub 等，
 不过它们也可以是可以被某应用使用的任何软件交付件。
 [服务目录](/zh/docs/concepts/extend-kubernetes/service-catalog/)
 提供了一种方法用来列举、制备和绑定到
-{{< glossary_tooltip text="服务代理商" term_id="service-broker" >}}
+{{< glossary_tooltip text="服务代理商（Service Brokers）" term_id="service-broker" >}}
 所提供的托管服务。
diff --git a/content/zh/docs/reference/glossary/manifest.md b/content/zh/docs/reference/glossary/manifest.md
@@ -1,5 +1,5 @@
 ---
-title: 清单
+title: 清单（Manifest）
 id: manifest
 date: 2019-06-28
 short_description: >
diff --git a/content/zh/docs/reference/glossary/master.md b/content/zh/docs/reference/glossary/master.md
@@ -31,4 +31,4 @@ tags:
 <!-- 
 The term is still being used by some provisioning tools, such as {{< glossary_tooltip text="kubeadm" term_id="kubeadm" >}}, and managed services, to {{< glossary_tooltip text="label" term_id="label" >}} {{< glossary_tooltip text="nodes" term_id="node" >}} with `kubernetes.io/role` and control placement of {{< glossary_tooltip text="control plane" term_id="control-plane" >}} {{< glossary_tooltip text="pods" term_id="pod" >}}.
 -->
-该术语仍被一些配置工具使用，如 {{< glossary_tooltip text="kubeadm" term_id="kubeadm" >}} 以及托管的服务，为 {{< glossary_tooltip text="节点" term_id="node" >}} 添加 `kubernetes.io/role` 的 {{< glossary_tooltip text="标签" term_id="label" >}}，以及管理控制平面 Pod 的调度。
+该术语仍被一些配置工具使用，如 {{< glossary_tooltip text="kubeadm" term_id="kubeadm" >}} 以及托管的服务，为 {{< glossary_tooltip text="节点（nodes）" term_id="node" >}} 添加 `kubernetes.io/role` 的 {{< glossary_tooltip text="标签（label）" term_id="label" >}}，以及管理控制平面 Pod 的调度。
diff --git a/content/zh/docs/reference/glossary/member.md b/content/zh/docs/reference/glossary/member.md
@@ -1,5 +1,5 @@
 ---
-title: 成员
+title: 成员（Member）
 id: member
 date: 2018-04-12
 full_link: 
@@ -30,13 +30,13 @@ tags:
  A continuously active {{< glossary_tooltip text="contributor" term_id="contributor" >}} in the K8s community.
 -->
 
- K8s 社区中持续活跃的贡献者。
+ K8s 社区中持续活跃的{{< glossary_tooltip text="贡献者（contributor）" term_id="contributor" >}}。
 
 <!--more--> 
 
 <!--
 Members can have issues and PRs assigned to them and participate in {{< glossary_tooltip text="special interest groups (SIGs)" term_id="sig" >}} through GitHub teams. Pre-submit tests are automatically run for members' PRs. A member is expected to remain an active contributor to the community.
 -->
 
-可以将问题单（issue）和 PR 指派给成员，成员也可以通过 GitHub 小组加入 {{< glossary_tooltip text="特别兴趣小组 (SIGs)" term_id="sig" >}}。针对成员所提交的 PR，系统自动运行提交前测试。成员应该是持续活跃的社区贡献者。
+可以将问题单（issue）和 PR 指派给成员（Member），成员（Member）也可以通过 GitHub 小组加入 {{< glossary_tooltip text="特别兴趣小组 (SIGs)" term_id="sig" >}}。针对成员（Member）所提交的 PR，系统自动运行提交前测试。成员（Member）应该是持续活跃的社区贡献者。
 
diff --git a/content/zh/docs/reference/glossary/minikube.md b/content/zh/docs/reference/glossary/minikube.md
@@ -38,6 +38,10 @@ Minikube 是用来在本地运行 Kubernetes 的一种工具。
 
 <!--
 Minikube runs a single-node cluster inside a VM on your computer.
+You can use Minikube to
+[try Kubernetes in a learning environment](/docs/setup/learning-environment/).
 -->
 
 Minikube 在用户计算机上的一个虚拟机内运行单节点 Kubernetes 集群。
+你可以使用 Minikube 
+[在学习环境中尝试 Kubernetes](/zh/docs/setup/learning-environment/).
diff --git a/content/zh/docs/reference/glossary/mirror-pod.md b/content/zh/docs/reference/glossary/mirror-pod.md
@@ -1,9 +1,9 @@
 ---
-title: 静态 Pod
+title: 镜像 Pod（Mirror Pod）
 id: 静态-pod
 date: 2019-08-06
 short_description: >
-  API 服务器中的一个对象，用于跟踪 kubelet 上的静态容器。
+  API 服务器中的一个对象，用于跟踪 kubelet 上的静态 pod。
 
 aka:
 tags:
@@ -27,7 +27,8 @@ 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" >}}
 -->
- kubelet 使用一个对象 {{< glossary_tooltip text="pod" term_id="pod" >}} 来代表 {{< 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" >}} 对象。
 
 <!--more-->
 <!--更多-->
@@ -43,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 守护进程继续运行它）。
diff --git a/content/zh/docs/reference/glossary/name.md b/content/zh/docs/reference/glossary/name.md
@@ -1,5 +1,5 @@
 ---
-title: 名称
+title: 名称（Name）
 id: name
 date: 2018-04-12
 full_link: /zh/docs/concepts/overview/working-with-objects/names/
@@ -16,7 +16,7 @@ tags:
 title: Name
 id: name
 date: 2018-04-12
-full_link: /zh/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`.
 
@@ -38,4 +38,4 @@ tags:
 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.
 -->
 
-一次只能有一个给定类型的对象具有给定的名称。但是，如果删除对象，则可以创建同名的新对象。
+某一时刻，只能有一个给定类型的对象具有给定的名称。但是，如果删除该对象，则可以创建同名的新对象。
diff --git a/content/zh/docs/reference/glossary/namespace.md b/content/zh/docs/reference/glossary/namespace.md
@@ -1,10 +1,10 @@
 ---
-title: 命名空间
+title: 名字空间（Namespace）
 id: namespace
 date: 2018-04-12
 full_link: /zh/docs/concepts/overview/working-with-objects/namespaces/
 short_description: >
-  命名空间是 Kubernetes 为了在同一物理集群上支持多个虚拟集群而使用的一种抽象。
+  名字空间是 Kubernetes 为了在同一物理集群上支持多个虚拟集群而使用的一种抽象。
 
 aka: 
 tags:
@@ -16,7 +16,7 @@ tags:
 title: Namespace
 id: namespace
 date: 2018-04-12
-full_link: /zh/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 multiple virtual clusters on the same physical cluster.
 
@@ -30,12 +30,12 @@ tags:
  An abstraction used by Kubernetes to support multiple virtual clusters on the same physical {{< glossary_tooltip text="cluster" term_id="cluster" >}}.
 -->
 
-命名空间是 Kubernetes 为了在同一物理集群上支持多个虚拟集群而使用的一种抽象。
+名字空间是 Kubernetes 为了在同一物理集群上支持多个虚拟集群而使用的一种抽象。
 
 <!--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.
 -->
 
-命名空间用来组织集群中对象，并为集群资源划分提供了一种方法。同一命名空间内的资源名称必须唯一，但跨命名空间时不作要求。
+名字空间用来组织集群中对象，并为集群资源划分提供了一种方法。同一名字空间内的资源名称必须唯一，但跨名字空间时不作要求。
diff --git a/content/zh/docs/reference/glossary/network-policy.md b/content/zh/docs/reference/glossary/network-policy.md
@@ -18,7 +18,7 @@ tags:
 title: Network Policy
 id: network-policy
 date: 2018-04-12
-full_link: /zh/docs/concepts/services-networking/network-policies/
+full_link: /docs/concepts/services-networking/network-policies/
 short_description: >
   A specification of how groups of Pods are allowed to communicate with each other and with other network endpoints.
 
diff --git a/content/zh/docs/reference/glossary/node.md b/content/zh/docs/reference/glossary/node.md
@@ -38,7 +38,7 @@ In early Kubernetes versions, Nodes were called "Minions".
 -->
 工作机器可以是虚拟机也可以是物理机，取决于集群的配置。
 其上部署了运行 {{< glossary_tooltip text="Pods" term_id="pod" >}}
-所必需的本地守护进程或{{< glossary_tooltip text="服务" term_id="service" >}}，
+所必需的本地守护进程或服务，
 并由主控组件来管理。
 节点上的的守护进程包括 {{< glossary_tooltip text="kubelet" term_id="kubelet" >}}、
 {{< glossary_tooltip text="kube-proxy" term_id="kube-proxy" >}}
diff --git a/content/zh/docs/reference/glossary/object.md b/content/zh/docs/reference/glossary/object.md
@@ -1,8 +1,8 @@
 ---
-title: 对象
+title: 对象（Object）
 id: object
 date: 2020-10-12
-full_link: https://kubernetes.io/docs/concepts/overview/working-with-objects/kubernetes-objects/#kubernetes-objects
+full_link: /zh/docs/concepts/overview/working-with-objects/kubernetes-objects/#kubernetes-objects
 short_description: >
    Kubernetes 系统中的实体, 代表了集群的部分状态。
 aka: 
@@ -37,6 +37,6 @@ By creating an object, you're effectively telling the Kubernetes system what you
 your cluster's workload to look like; this is your cluster's desired state.
 -->
 Kubernetes 对象通常是一个“目标记录”-一旦你创建了一个对象，Kubernetes 
-{{< glossary_tooltip text="控制平面" term_id="control-plane" >}} 
+{{< glossary_tooltip text="控制平面（Control Plane）" term_id="control-plane" >}} 
 不断工作，以确保它代表的项目确实存在。
 创建一个对象相当于告知 Kubernetes 系统：你期望这部分集群负载看起来像什么；这也就是你集群的期望状态。
diff --git a/content/zh/docs/reference/glossary/operator-pattern.md b/content/zh/docs/reference/glossary/operator-pattern.md
@@ -15,7 +15,7 @@ tags:
 title: Operator pattern
 id: operator-pattern
 date: 2019-05-21
-full_link: /zh/docs/concepts/extend-kubernetes/operator/
+full_link: /docs/concepts/extend-kubernetes/operator/
 short_description: >
   A specialized controller used to manage a custom resource
 
diff --git a/content/zh/docs/reference/glossary/persistent-volume-claim.md b/content/zh/docs/reference/glossary/persistent-volume-claim.md
@@ -1,8 +1,8 @@
 ---
-title: 持久卷申领
+title: 持久卷申领（Persistent Volume Claim）
 id: persistent-volume-claim
 date: 2018-04-12
-full_link: /docs/concepts/storage/persistent-volumes/
+full_link: /zh/docs/concepts/storage/persistent-volumes/
 short_description: >
   声明在持久卷中定义的存储资源，以便可以将其挂载为容器中的卷。
 
@@ -27,13 +27,13 @@ tags:
 -->
 
 <!--
- Claims storage resources defined in a PersistentVolume so that it can be mounted as a volume in a container.
+ Claims storage resources defined in a {{< glossary_tooltip text="PersistentVolume" term_id="persistent-volume" >}} so that it can be mounted as a volume in a {{< glossary_tooltip text="container" term_id="container" >}}.
 -->
-申领持久卷中定义的存储资源，以便可以将其挂载为容器中的卷。
+申领{{< glossary_tooltip text="持久卷（PersistentVolume）" term_id="persistent-volume" >}}中定义的存储资源，以便可以将其挂载为{{< glossary_tooltip text="容器（container）" term_id="container" >}}中的卷。
 
 <!--more--> 
 
 <!--
-Specifies the amount of storage, how the storage will be accessed (read-only, read-write and/or exclusive) and how it is reclaimed (retained, recycled or deleted). Details of the storage itself are in the PersistentVolume specification.
+Specifies the amount of storage, how the storage will be accessed (read-only, read-write and/or exclusive) and how it is reclaimed (retained, recycled or deleted). Details of the storage itself are described in the PersistentVolume object.
 -->
-指定存储的数量，如何访问存储（只读、读写或独占）以及如何回收存储（保留、回收或删除）。存储本身的详细信息在 PersistentVolume 规范中。
+指定存储的数量，如何访问存储（只读、读写或独占）以及如何回收存储（保留、回收或删除）。存储本身的详细信息在 PersistentVolume 对象中。
diff --git a/content/zh/docs/reference/glossary/persistent-volume.md b/content/zh/docs/reference/glossary/persistent-volume.md
@@ -1,8 +1,8 @@
 ---
-title: 持久卷
+title: 持久卷（Persistent Volume）
 id: persistent-volume
 date: 2018-04-12
-full_link: /docs/concepts/storage/persistent-volumes/
+full_link: /zh/docs/concepts/storage/persistent-volumes/
 short_description: >
   持久卷是代表集群中一块存储空间的 API 对象。 它是通用的、可插拔的、并且不受单个 Pod 生命周期约束的持久化资源。
 
@@ -32,7 +32,7 @@ tags:
  An API object that represents a piece of storage in the cluster. Available as a general, pluggable resource that persists beyond the lifecycle of any individual {{< glossary_tooltip text="Pod" term_id="pod" >}}.
 -->
 
-持久卷是代表集群中一块存储空间的 API 对象。 它是通用的、可插拔的、并且不受单个 Pod 生命周期约束的持久化资源。
+持久卷是代表集群中一块存储空间的 API 对象。 它是通用的、可插拔的、并且不受单个 {{< glossary_tooltip text="Pod" term_id="pod" >}} 生命周期约束的持久化资源。
 
 <!--more--> 
 
diff --git a/content/zh/docs/reference/glossary/pod-disruption-budget.md b/content/zh/docs/reference/glossary/pod-disruption-budget.md
diff --git a/content/zh/docs/reference/glossary/pod-lifecycle.md b/content/zh/docs/reference/glossary/pod-lifecycle.md
diff --git a/content/zh/docs/reference/glossary/pod-priority.md b/content/zh/docs/reference/glossary/pod-priority.md
diff --git a/content/zh/docs/reference/glossary/pod-security-policy.md b/content/zh/docs/reference/glossary/pod-security-policy.md
diff --git a/content/zh/docs/reference/glossary/pod.md b/content/zh/docs/reference/glossary/pod.md
diff --git a/content/zh/docs/reference/glossary/proxy.md b/content/zh/docs/reference/glossary/proxy.md
