Merge pull request #34509 from howieyuen/ref-1
[zh]Update reference pages(part-1) for links with '/zh/' prefix, using new prefix '/zh-cn/'
This commit is contained in:
@@ -2,7 +2,7 @@
|
||||
title: 附加组件(Add-ons)
|
||||
id: addons
|
||||
date: 2019-12-15
|
||||
full_link: /zh/docs/concepts/cluster-administration/addons/
|
||||
full_link: /zh-cn/docs/concepts/cluster-administration/addons/
|
||||
short_description: >
|
||||
扩展 Kubernetes 功能的资源。
|
||||
|
||||
@@ -37,4 +37,4 @@ tags:
|
||||
<!--
|
||||
[Installing addons](/docs/concepts/cluster-administration/addons/) explains more about using add-ons with your cluster, and lists some popular add-ons.
|
||||
-->
|
||||
[安装附加组件](/zh/docs/concepts/cluster-administration/addons/) 阐释了更多关于如何在集群内使用附加组件,并列出了一些流行的附加组件。
|
||||
[安装附加组件](/zh-cn/docs/concepts/cluster-administration/addons/) 阐释了更多关于如何在集群内使用附加组件,并列出了一些流行的附加组件。
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: 准入控制器(Admission Controller)
|
||||
id: admission-controller
|
||||
date: 2019-06-28
|
||||
full_link: /zh/docs/reference/access-authn-authz/admission-controllers/
|
||||
full_link: /zh-cn/docs/reference/access-authn-authz/admission-controllers/
|
||||
short_description: >
|
||||
在对象持久化之前拦截 Kubernetes Api 服务器请求的一段代码
|
||||
aka:
|
||||
@@ -47,4 +47,4 @@ validating controllers may not.
|
||||
准入控制器可针对 Kubernetes Api 服务器进行配置,可以执行验证,变更或两者都执行。任何准入控制器都可以拒绝访问请求。
|
||||
变更(mutating)控制器可以修改其允许的对象,验证(validating)控制器则不可以。
|
||||
|
||||
* [Kubernetes 文档中的准入控制器](/zh/docs/reference/access-authn-authz/admission-controllers/)
|
||||
* [Kubernetes 文档中的准入控制器](/zh-cn/docs/reference/access-authn-authz/admission-controllers/)
|
||||
@@ -36,8 +36,8 @@ There are two kinds of affinity:
|
||||
* [node affinity](/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity)
|
||||
* [pod-to-pod affinity](/docs/concepts/scheduling-eviction/assign-pod-node/#inter-pod-affinity-and-anti-affinity)
|
||||
-->
|
||||
* [节点亲和性](/zh/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity)
|
||||
* [Pod 间亲和性](/zh/docs/concepts/scheduling-eviction/assign-pod-node/#inter-pod-affinity-and-anti-affinity)
|
||||
* [节点亲和性](/zh-cn/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity)
|
||||
* [Pod 间亲和性](/zh-cn/docs/concepts/scheduling-eviction/assign-pod-node/#inter-pod-affinity-and-anti-affinity)
|
||||
|
||||
<!--
|
||||
The rules are defined using the Kubernetes {{< glossary_tooltip term_id="label" text="labels">}},
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: 聚合层(Aggregation Layer)
|
||||
id: aggregation-layer
|
||||
date: 2018-10-08
|
||||
full_link: /zh/docs/concepts/extend-kubernetes/api-extension/apiserver-aggregation/
|
||||
full_link: /zh-cn/docs/concepts/extend-kubernetes/api-extension/apiserver-aggregation/
|
||||
short_description: >
|
||||
聚合层允许你在自己的集群上安装额外的 Kubernetes 风格的 API。
|
||||
|
||||
@@ -45,5 +45,5 @@ tags:
|
||||
When you've configured the {{< glossary_tooltip text="Kubernetes API Server" term_id="kube-apiserver" >}} to [support additional APIs](/docs/tasks/extend-kubernetes/configure-aggregation-layer/), you can add `APIService` objects to "claim" a URL path in the Kubernetes API.
|
||||
-->
|
||||
|
||||
当你配置了 {{< glossary_tooltip text="Kubernetes API Server" term_id="kube-apiserver" >}} 来 [支持额外的 API](/zh/docs/tasks/extend-kubernetes/configure-aggregation-layer/),
|
||||
当你配置了 {{< glossary_tooltip text="Kubernetes API Server" term_id="kube-apiserver" >}} 来 [支持额外的 API](/zh-cn/docs/tasks/extend-kubernetes/configure-aggregation-layer/),
|
||||
你就可以在 Kubernetes API 中增加 `APIService` 对象来 "申领(Claim)" 一个 URL 路径。
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: 注解(Annotation)
|
||||
id: annotation
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/overview/working-with-objects/annotations/
|
||||
full_link: /zh-cn/docs/concepts/overview/working-with-objects/annotations/
|
||||
short_description: >
|
||||
注解是以键值对的形式给资源对象附加随机的无法标识的元数据。
|
||||
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: API 发起的驱逐
|
||||
id: api-eviction
|
||||
date: 2021-04-27
|
||||
full_link: /zh/docs/concepts/scheduling-eviction/pod-eviction/#api-eviction
|
||||
full_link: /zh-cn/docs/concepts/scheduling-eviction/pod-eviction/#api-eviction
|
||||
short_description: >
|
||||
API 发起的驱逐是一个先调用 Eviction API 创建驱逐对象,再由该对象体面地中止 Pod 的过程。
|
||||
aka:
|
||||
@@ -46,13 +46,13 @@ API-initiated eviction is not the same as [node-pressure eviction](/docs/concept
|
||||
你可以通过 kube-apiserver 的客户端,比如 `kubectl drain` 这样的命令,直接调用 Eviction API 发起驱逐。
|
||||
当 `Eviction` 对象创建出来之后,该对象将驱动 API 服务器终止选定的Pod。
|
||||
|
||||
API 发起的驱逐取决于你配置的 [`PodDisruptionBudgets`](/zh/docs/tasks/run-application/configure-pdb/)
|
||||
和 [`terminationGracePeriodSeconds`](/zh/docs/concepts/workloads/pods/pod-lifecycle#pod-termination)。
|
||||
API 发起的驱逐取决于你配置的 [`PodDisruptionBudgets`](/zh-cn/docs/tasks/run-application/configure-pdb/)
|
||||
和 [`terminationGracePeriodSeconds`](/zh-cn/docs/concepts/workloads/pods/pod-lifecycle#pod-termination)。
|
||||
|
||||
API 发起的驱逐不同于
|
||||
[节点压力引发的驱逐](/zh/docs/concepts/scheduling-eviction/eviction/#kubelet-eviction)。
|
||||
[节点压力引发的驱逐](/zh-cn/docs/concepts/scheduling-eviction/eviction/#kubelet-eviction)。
|
||||
|
||||
<!--
|
||||
* See [API-initiated eviction](/docs/concepts/scheduling-eviction/api-eviction/) for more information.
|
||||
-->
|
||||
* 有关详细信息,请参阅 [API 发起的驱逐](/zh/docs/concepts/scheduling-eviction/api-eviction/)。
|
||||
* 有关详细信息,请参阅 [API 发起的驱逐](/zh-cn/docs/concepts/scheduling-eviction/api-eviction/)。
|
||||
@@ -2,7 +2,7 @@
|
||||
title: API Group
|
||||
id: api-group
|
||||
date: 2019-09-02
|
||||
full_link: /zh/docs/concepts/overview/kubernetes-api/#api-groups-and-versioning
|
||||
full_link: /zh-cn/docs/concepts/overview/kubernetes-api/#api-groups-and-versioning
|
||||
short_description: >
|
||||
Kubernetes API 中的一组相关路径
|
||||
|
||||
@@ -47,4 +47,4 @@ API group 在 REST 路径和序列化对象的 `apiVersion` 字段中指定。
|
||||
<!--
|
||||
* Read [API Group](/docs/concepts/overview/kubernetes-api/#api-groups-and-versioning) for more information.
|
||||
-->
|
||||
* 阅读 [API Group](/zh/docs/concepts/overview/kubernetes-api/#api-groups-and-versioning) 了解更多信息。
|
||||
* 阅读 [API Group](/zh-cn/docs/concepts/overview/kubernetes-api/#api-groups-and-versioning) 了解更多信息。
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: 证书(Certificate)
|
||||
id: certificate
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/tasks/tls/managing-tls-in-a-cluster/
|
||||
full_link: /zh-cn/docs/tasks/tls/managing-tls-in-a-cluster/
|
||||
short_description: >
|
||||
证书是个安全加密文件,用来确认对 Kubernetes 集群访问的合法性。
|
||||
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: 云控制器管理器(Cloud Controller Manager)
|
||||
id: cloud-controller-manager
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/architecture/cloud-controller/
|
||||
full_link: /zh-cn/docs/concepts/architecture/cloud-controller/
|
||||
short_description: >
|
||||
将 Kubernetes 与第三方云提供商进行集成的控制面组件。
|
||||
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: 容器网络接口(CNI)
|
||||
id: cni
|
||||
date: 2018-05-25
|
||||
full_link: /zh/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#cni
|
||||
full_link: /zh-cn/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#cni
|
||||
short_description: >
|
||||
容器网络接口 (CNI) 插件是遵循 appc/CNI 协议的一类网络插件。
|
||||
|
||||
@@ -41,4 +41,4 @@ tags:
|
||||
* For information on Kubernetes and CNI, see ["Network plugins"](/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#cni).
|
||||
-->
|
||||
|
||||
* 想了解 Kubernetes 和 CNI 请参考 ["网络插件"](/zh/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#cni)。
|
||||
* 想了解 Kubernetes 和 CNI 请参考 ["网络插件"](/zh-cn/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#cni)。
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: ConfigMap
|
||||
id: configmap
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/tasks/configure-pod-container/configure-pod-configmap/
|
||||
full_link: /zh-cn/docs/tasks/configure-pod-container/configure-pod-configmap/
|
||||
short_description: >
|
||||
ConfigMap 是一种 API 对象,用来将非机密性的数据保存到键值对中。使用时可以用作环境变量、命令行参数或者存储卷中的配置文件。
|
||||
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: 容器环境变量(Container Environment Variables)
|
||||
id: container-env-variables
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/containers/container-environment/
|
||||
full_link: /zh-cn/docs/concepts/containers/container-environment/
|
||||
short_description: >
|
||||
容器环境变量提供了 name=value 形式的、运行容器化应用所必须的一些重要信息。
|
||||
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: 容器生命周期钩子(Container Lifecycle Hooks)
|
||||
id: container-lifecycle-hooks
|
||||
date: 2018-10-08
|
||||
full_link: /zh/docs/concepts/containers/container-lifecycle-hooks/
|
||||
full_link: /zh-cn/docs/concepts/containers/container-lifecycle-hooks/
|
||||
short_description: >
|
||||
生命周期钩子暴露容器管理生命周期中的事件,允许用户在事件发生时运行代码。
|
||||
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: 容器运行时接口
|
||||
id: container-runtime-interface
|
||||
date: 2021-11-24
|
||||
full_link: /zh/docs/concepts/architecture/cri
|
||||
full_link: /zh-cn/docs/concepts/architecture/cri
|
||||
short_description: >
|
||||
kubelet 和容器运行时之间通信的主要协议。
|
||||
|
||||
@@ -37,6 +37,6 @@ The Kubernetes Container Runtime Interface (CRI) defines the main
|
||||
{{< glossary_tooltip text="container runtime" term_id="container-runtime" >}}.
|
||||
-->
|
||||
Kubernetes 容器运行时接口(CRI)定义了主要 [gRPC](https://grpc.io) 协议,
|
||||
用于[集群组件](/zh/docs/concepts/overview/components/#node-components)
|
||||
用于[集群组件](/zh-cn/docs/concepts/overview/components/#node-components)
|
||||
{{< glossary_tooltip text="kubelet" term_id="kubelet" >}} 和
|
||||
{{< glossary_tooltip text="容器运行时" term_id="container-runtime" >}}。
|
||||
@@ -2,7 +2,7 @@
|
||||
title: 容器运行时(Container Runtime)
|
||||
id: container-runtime
|
||||
date: 2019-06-05
|
||||
full_link: /zh/docs/setup/production-environment/container-runtimes
|
||||
full_link: /zh-cn/docs/setup/production-environment/container-runtimes
|
||||
short_description: >
|
||||
容器运行时是负责运行容器的软件。
|
||||
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: 容器(Container)
|
||||
id: container
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/overview/what-is-kubernetes/#why-containers
|
||||
full_link: /zh-cn/docs/concepts/overview/what-is-kubernetes/#why-containers
|
||||
short_description: >
|
||||
容器是可移植、可执行的轻量级的镜像,镜像中包含软件及其相关依赖。
|
||||
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: 控制器(Controller)
|
||||
id: controller
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/architecture/controller/
|
||||
full_link: /zh-cn/docs/concepts/architecture/controller/
|
||||
short_description: >
|
||||
控制器通过 apiserver 监控集群的公共状态,并致力于将当前状态转变为期望的状态。
|
||||
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: 容器运行时接口(CRI)
|
||||
id: cri
|
||||
date: 2019-03-07
|
||||
full_link: /zh/docs/concepts/overview/components/#container-runtime
|
||||
full_link: /zh-cn/docs/concepts/overview/components/#container-runtime
|
||||
short_description: >
|
||||
一组与 kubelet 集成的容器运行时 API
|
||||
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: 周期调度任务(CronJob)
|
||||
id: cronjob
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/workloads/controllers/cron-jobs/
|
||||
full_link: /zh-cn/docs/concepts/workloads/controllers/cron-jobs/
|
||||
short_description: >
|
||||
周期调度的任务(作业)。
|
||||
|
||||
@@ -32,7 +32,7 @@ tags:
|
||||
Manages a [Job](/docs/concepts/workloads/controllers/job/) that runs on a periodic schedule.
|
||||
-->
|
||||
|
||||
管理定期运行的 [任务](/zh/docs/concepts/workloads/controllers/job/)。
|
||||
管理定期运行的 [任务](/zh-cn/docs/concepts/workloads/controllers/job/)。
|
||||
|
||||
<!--more-->
|
||||
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: 容器存储接口(Container Storage Interface,CSI)
|
||||
id: csi
|
||||
date: 2018-06-25
|
||||
full_link: /zh/docs/concepts/storage/volumes/#csi
|
||||
full_link: /zh-cn/docs/concepts/storage/volumes/#csi
|
||||
short_description: >
|
||||
容器存储接口 (CSI)定义了存储系统暴露给容器的标准接口。
|
||||
|
||||
@@ -48,5 +48,5 @@ CSI 允许存储驱动提供商为 Kubernetes 创建定制化的存储插件,
|
||||
[将它部署到你的集群上](https://kubernetes-csi.github.io/docs/deploying.html)。
|
||||
然后你才能创建使用该 CSI 驱动的 {{< glossary_tooltip text="Storage Class" term_id="storage-class" >}} 。
|
||||
|
||||
* [Kubernetes 文档中关于 CSI 的描述](/zh/docs/concepts/storage/volumes/#csi)
|
||||
* [Kubernetes 文档中关于 CSI 的描述](/zh-cn/docs/concepts/storage/volumes/#csi)
|
||||
* [可用的 CSI 驱动列表](https://kubernetes-csi.github.io/docs/drivers.html)
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: CustomResourceDefinition
|
||||
id: CustomResourceDefinition
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/
|
||||
full_link: /zh-cn/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/
|
||||
short_description: >
|
||||
通过定制化的代码给你的 Kubernetes API 服务器增加资源对象,而无需编译完整的定制 API 服务器。
|
||||
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: DaemonSet
|
||||
id: daemonset
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/workloads/controllers/daemonset/
|
||||
full_link: /zh-cn/docs/concepts/workloads/controllers/daemonset/
|
||||
short_description: >
|
||||
确保 Pod 的副本在集群中的一组节点上运行。
|
||||
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: Deployment
|
||||
id: deployment
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/workloads/controllers/deployment/
|
||||
full_link: /zh-cn/docs/concepts/workloads/controllers/deployment/
|
||||
short_description: >
|
||||
Deployment 是管理应用副本的 API 对象。
|
||||
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: 设备插件(Device Plugin)
|
||||
id: device-plugin
|
||||
date: 2019-02-02
|
||||
full_link: /zh/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/
|
||||
full_link: /zh-cn/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/
|
||||
short_description: >
|
||||
一种软件扩展,可以使 Pod 访问由特定厂商初始化或者安装的设备。
|
||||
aka:
|
||||
@@ -49,4 +49,4 @@ See
|
||||
[Device Plugins](/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/)
|
||||
for more information.
|
||||
-->
|
||||
更多信息请查阅[设备插件](/zh/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/)
|
||||
更多信息请查阅[设备插件](/zh-cn/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/)
|
||||
@@ -2,7 +2,7 @@
|
||||
title: 干扰(Disruption)
|
||||
id: disruption
|
||||
date: 2019-09-10
|
||||
full_link: /zh/docs/concepts/workloads/pods/disruptions/
|
||||
full_link: /zh-cn/docs/concepts/workloads/pods/disruptions/
|
||||
short_description: >
|
||||
导致 Pod 服务停止的事件。
|
||||
aka:
|
||||
@@ -44,4 +44,4 @@ See [Disruptions](/docs/concepts/workloads/pods/disruptions/) for more informati
|
||||
如果你作为一个集群操作人员,销毁了一个从属于某个应用的 Pod, Kubernetes 视之为**自愿干扰(Voluntary Disruption)**。
|
||||
如果由于节点故障 或者影响更大区域故障的断电导致 Pod 离线,kubernetes 视之为**非愿干扰(Involuntary Disruption)**。
|
||||
|
||||
更多信息请查阅[Disruptions](/zh/docs/concepts/workloads/pods/disruptions/)
|
||||
更多信息请查阅[Disruptions](/zh-cn/docs/concepts/workloads/pods/disruptions/)
|
||||
@@ -2,7 +2,7 @@
|
||||
title: Docker
|
||||
id: docker
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/reference/kubectl/docker-cli-to-kubectl/
|
||||
full_link: /zh-cn/docs/reference/kubectl/docker-cli-to-kubectl/
|
||||
short_description: >
|
||||
Docker 是一种可以提供操作系统级别虚拟化(也称作容器)的软件技术。
|
||||
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: Dockershim
|
||||
id: dockershim
|
||||
date: 2022-04-15
|
||||
full_link: /zh/dockershim
|
||||
full_link: /zh-cn/dockershim
|
||||
short_description: >
|
||||
dockershim 是 Kubernetes v1.23 及之前版本中的一个组件,Kubernetes 系统组件通过它与 Docker Engine 通信。
|
||||
|
||||
@@ -37,4 +37,4 @@ Kubernetes 系统组件通过它与 {{< glossary_tooltip text="Docker Engine" te
|
||||
Starting with version 1.24, dockershim has been removed from Kubernetes. For more information, see [Dockershim FAQ](/dockershim).
|
||||
-->
|
||||
从 Kubernetes v1.24 开始,dockershim 已从 Kubernetes 中移除.
|
||||
想了解更多信息,可参考[移除 Dockershim 的常见问题](/zh/dockershim)。
|
||||
想了解更多信息,可参考[移除 Dockershim 的常见问题](/zh-cn/dockershim)。
|
||||
@@ -2,7 +2,7 @@
|
||||
title: 动态卷供应(Dynamic Volume Provisioning)
|
||||
id: dynamicvolumeprovisioning
|
||||
date: 2018-04-12
|
||||
full_link: /zh/docs/concepts/storage/dynamic-provisioning/
|
||||
full_link: /zh-cn/docs/concepts/storage/dynamic-provisioning/
|
||||
short_description: >
|
||||
允许用户请求自动创建存储卷。
|
||||
|
||||
|
||||
Reference in New Issue
Block a user