Merge pull request #34511 from howieyuen/ref-3
[zh]Update reference pages(part-3) for links with '/zh/' prefix, using new prefix '/zh-cn/'
This commit is contained in:
commit
3aa475b6e6
|
@ -2,7 +2,7 @@
|
||||||
title: Operator 模式
|
title: Operator 模式
|
||||||
id: operator-pattern
|
id: operator-pattern
|
||||||
date: 2019-05-21
|
date: 2019-05-21
|
||||||
full_link: /zh/docs/concepts/extend-kubernetes/operator/
|
full_link: /zh-cn/docs/concepts/extend-kubernetes/operator/
|
||||||
short_description: >
|
short_description: >
|
||||||
一种用于管理自定义资源的专用控制器
|
一种用于管理自定义资源的专用控制器
|
||||||
|
|
||||||
|
@ -28,7 +28,7 @@ The [operator pattern](/docs/concepts/extend-kubernetes/operator/) is a system
|
||||||
design that links a {{< glossary_tooltip term_id="controller" >}} to one or more custom
|
design that links a {{< glossary_tooltip term_id="controller" >}} to one or more custom
|
||||||
resources.
|
resources.
|
||||||
-->
|
-->
|
||||||
[operator 模式](/zh/docs/concepts/extend-kubernetes/operator/) 是一种系统设计,
|
[operator 模式](/zh-cn/docs/concepts/extend-kubernetes/operator/) 是一种系统设计,
|
||||||
将 {{< glossary_tooltip term_id="controller" >}} 关联到一个或多个自定义资源。
|
将 {{< glossary_tooltip term_id="controller" >}} 关联到一个或多个自定义资源。
|
||||||
<!--more-->
|
<!--more-->
|
||||||
|
|
||||||
|
|
|
@ -2,7 +2,7 @@
|
||||||
title: 持久卷申领(Persistent Volume Claim)
|
title: 持久卷申领(Persistent Volume Claim)
|
||||||
id: persistent-volume-claim
|
id: persistent-volume-claim
|
||||||
date: 2018-04-12
|
date: 2018-04-12
|
||||||
full_link: /zh/docs/concepts/storage/persistent-volumes/
|
full_link: /zh-cn/docs/concepts/storage/persistent-volumes/
|
||||||
short_description: >
|
short_description: >
|
||||||
声明在持久卷中定义的存储资源,以便可以将其挂载为容器中的卷。
|
声明在持久卷中定义的存储资源,以便可以将其挂载为容器中的卷。
|
||||||
|
|
||||||
|
|
|
@ -2,7 +2,7 @@
|
||||||
title: 持久卷(Persistent Volume)
|
title: 持久卷(Persistent Volume)
|
||||||
id: persistent-volume
|
id: persistent-volume
|
||||||
date: 2018-04-12
|
date: 2018-04-12
|
||||||
full_link: /zh/docs/concepts/storage/persistent-volumes/
|
full_link: /zh-cn/docs/concepts/storage/persistent-volumes/
|
||||||
short_description: >
|
short_description: >
|
||||||
持久卷是代表集群中一块存储空间的 API 对象。 它是通用的、可插拔的、并且不受单个 Pod 生命周期约束的持久化资源。
|
持久卷是代表集群中一块存储空间的 API 对象。 它是通用的、可插拔的、并且不受单个 Pod 生命周期约束的持久化资源。
|
||||||
|
|
||||||
|
|
|
@ -41,8 +41,8 @@ develop extensions which are contributed to the Kubernetes community.
|
||||||
Others develop closed-source commercial or site-specific extensions.
|
Others develop closed-source commercial or site-specific extensions.
|
||||||
-->
|
-->
|
||||||
|
|
||||||
平台开发人员可以使用[定制资源](/zh/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
|
平台开发人员可以使用[定制资源](/zh-cn/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
|
||||||
或[使用汇聚层扩展 Kubernetes API](/zh/docs/concepts/extend-kubernetes/api-extension/apiserver-aggregation/)
|
或[使用汇聚层扩展 Kubernetes API](/zh-cn/docs/concepts/extend-kubernetes/api-extension/apiserver-aggregation/)
|
||||||
来为其 Kubernetes 实例增加功能,特别是为其应用程序添加功能。
|
来为其 Kubernetes 实例增加功能,特别是为其应用程序添加功能。
|
||||||
一些平台开发人员也是 kubernetes {{< glossary_tooltip text="贡献者" term_id="contributor" >}},
|
一些平台开发人员也是 kubernetes {{< glossary_tooltip text="贡献者" term_id="contributor" >}},
|
||||||
他们会开发贡献给 Kubernetes 社区的扩展。
|
他们会开发贡献给 Kubernetes 社区的扩展。
|
||||||
|
|
|
@ -1,7 +1,7 @@
|
||||||
---
|
---
|
||||||
id: pod-disruption-budget
|
id: pod-disruption-budget
|
||||||
title: Pod Disruption Budget
|
title: Pod Disruption Budget
|
||||||
full-link: /zh/docs/concepts/workloads/pods/disruptions/
|
full-link: /zh-cn/docs/concepts/workloads/pods/disruptions/
|
||||||
date: 2019-02-12
|
date: 2019-02-12
|
||||||
short_description: >
|
short_description: >
|
||||||
Pod Disruption Budget 是这样一种对象:它保证在主动中断( voluntary disruptions)时,多实例应用的 {{< glossary_tooltip text="Pod" term_id="pod" >}} 不会少于一定的数量。
|
Pod Disruption Budget 是这样一种对象:它保证在主动中断( voluntary disruptions)时,多实例应用的 {{< glossary_tooltip text="Pod" term_id="pod" >}} 不会少于一定的数量。
|
||||||
|
@ -43,7 +43,7 @@ tags:
|
||||||
Involuntary disruptions cannot be prevented by PDBs; however they
|
Involuntary disruptions cannot be prevented by PDBs; however they
|
||||||
do count against the budget.
|
do count against the budget.
|
||||||
-->
|
-->
|
||||||
[Pod 干扰预算(Pod Disruption Budget,PDB)](/zh/docs/concepts/workloads/pods/disruptions/)
|
[Pod 干扰预算(Pod Disruption Budget,PDB)](/zh-cn/docs/concepts/workloads/pods/disruptions/)
|
||||||
使应用所有者能够为多实例应用创建一个对象,来确保一定数量的具有指定标签的 Pod 在任何时候都不会被主动驱逐。
|
使应用所有者能够为多实例应用创建一个对象,来确保一定数量的具有指定标签的 Pod 在任何时候都不会被主动驱逐。
|
||||||
<!--more-->
|
<!--more-->
|
||||||
PDB 无法防止非主动的中断,但是会计入预算(budget)。
|
PDB 无法防止非主动的中断,但是会计入预算(budget)。
|
||||||
|
|
|
@ -37,7 +37,7 @@ tags:
|
||||||
Pods on Nodes are terminated either voluntarily or involuntarily.
|
Pods on Nodes are terminated either voluntarily or involuntarily.
|
||||||
-->
|
-->
|
||||||
|
|
||||||
[pod 干扰](/zh/docs/concepts/workloads/pods/disruptions/) 是指节点上的 pod 被自愿或非自愿终止的过程。
|
[pod 干扰](/zh-cn/docs/concepts/workloads/pods/disruptions/) 是指节点上的 pod 被自愿或非自愿终止的过程。
|
||||||
|
|
||||||
<!--more-->
|
<!--more-->
|
||||||
|
|
||||||
|
|
|
@ -2,7 +2,7 @@
|
||||||
title: Pod 生命周期
|
title: Pod 生命周期
|
||||||
id: pod-lifecycle
|
id: pod-lifecycle
|
||||||
date: 2019-02-17
|
date: 2019-02-17
|
||||||
full-link: /zh/docs/concepts/workloads/pods/pod-lifecycle/
|
full-link: /zh-cn/docs/concepts/workloads/pods/pod-lifecycle/
|
||||||
related:
|
related:
|
||||||
- pod
|
- pod
|
||||||
- container
|
- container
|
||||||
|
@ -36,7 +36,7 @@ A high-level summary of what phase the Pod is in within its lifecyle.
|
||||||
<!--
|
<!--
|
||||||
The [Pod Lifecycle](/docs/concepts/workloads/pods/pod-lifecycle/) is defined by the states or phases of a Pod. There are five possible Pod phases: Pending, Running, Succeeded, Failed, and Unknown. A high-level description of the Pod state is summarized in the [PodStatus](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#podstatus-v1-core) `phase` field.
|
The [Pod Lifecycle](/docs/concepts/workloads/pods/pod-lifecycle/) is defined by the states or phases of a Pod. There are five possible Pod phases: Pending, Running, Succeeded, Failed, and Unknown. A high-level description of the Pod state is summarized in the [PodStatus](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#podstatus-v1-core) `phase` field.
|
||||||
-->
|
-->
|
||||||
[Pod 生命周期](/zh/docs/concepts/workloads/pods/pod-lifecycle/) 是关于 Pod
|
[Pod 生命周期](/zh-cn/docs/concepts/workloads/pods/pod-lifecycle/) 是关于 Pod
|
||||||
处于哪个阶段的概述。包含了下面5种可能的的阶段: Running、Pending、Succeeded、
|
处于哪个阶段的概述。包含了下面5种可能的的阶段: Running、Pending、Succeeded、
|
||||||
Failed、Unknown。关于 Pod 的阶段的更高级描述请查阅
|
Failed、Unknown。关于 Pod 的阶段的更高级描述请查阅
|
||||||
[PodStatus](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#podstatus-v1-core) `phase` 字段。
|
[PodStatus](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#podstatus-v1-core) `phase` 字段。
|
||||||
|
|
|
@ -2,7 +2,7 @@
|
||||||
title: Pod 优先级(Pod Priority)
|
title: Pod 优先级(Pod Priority)
|
||||||
id: pod-priority
|
id: pod-priority
|
||||||
date: 2019-01-31
|
date: 2019-01-31
|
||||||
full_link: /zh/docs/concepts/scheduling-eviction/pod-priority-preemption/#pod-priority
|
full_link: /zh-cn/docs/concepts/scheduling-eviction/pod-priority-preemption/#pod-priority
|
||||||
short_description: >
|
short_description: >
|
||||||
Pod 优先级表示一个 Pod 相对于其他 Pod 的重要性。
|
Pod 优先级表示一个 Pod 相对于其他 Pod 的重要性。
|
||||||
|
|
||||||
|
@ -34,7 +34,7 @@ tags:
|
||||||
<!--
|
<!--
|
||||||
[Pod Priority](/docs/concepts/scheduling-eviction/pod-priority-preemption/#pod-priority) gives the ability to set scheduling priority of a Pod to be higher and lower than other Pods — an important feature for production clusters workload.
|
[Pod Priority](/docs/concepts/scheduling-eviction/pod-priority-preemption/#pod-priority) gives the ability to set scheduling priority of a Pod to be higher and lower than other Pods — an important feature for production clusters workload.
|
||||||
-->
|
-->
|
||||||
[Pod 优先级](/zh/docs/concepts/scheduling-eviction/pod-priority-preemption/#pod-priority)
|
[Pod 优先级](/zh-cn/docs/concepts/scheduling-eviction/pod-priority-preemption/#pod-priority)
|
||||||
允许用户为 Pod 设置高于或低于其他 Pod 的优先级 -- 这对于生产集群
|
允许用户为 Pod 设置高于或低于其他 Pod 的优先级 -- 这对于生产集群
|
||||||
工作负载而言是一个重要的特性。
|
工作负载而言是一个重要的特性。
|
||||||
|
|
||||||
|
|
|
@ -2,7 +2,7 @@
|
||||||
title: Pod 安全策略
|
title: Pod 安全策略
|
||||||
id: pod-security-policy
|
id: pod-security-policy
|
||||||
date: 2018-04-12
|
date: 2018-04-12
|
||||||
full_link: /zh/docs/concepts/security/pod-security-policy/
|
full_link: /zh-cn/docs/concepts/security/pod-security-policy/
|
||||||
short_description: >
|
short_description: >
|
||||||
为 Pod 的创建和更新操作启用细粒度的授权。
|
为 Pod 的创建和更新操作启用细粒度的授权。
|
||||||
|
|
||||||
|
@ -47,5 +47,5 @@ Pod 安全策略是集群级别的资源,它控制着 Pod 规约中的安全
|
||||||
PodSecurityPolicy is deprecated as of Kubernetes v1.21, and will be removed in v1.25. We recommend migrating to [Pod Security Admission](/docs/concepts/security/pod-security-admission/), or a 3rd party admission plugin.
|
PodSecurityPolicy is deprecated as of Kubernetes v1.21, and will be removed in v1.25. We recommend migrating to [Pod Security Admission](/docs/concepts/security/pod-security-admission/), or a 3rd party admission plugin.
|
||||||
-->
|
-->
|
||||||
PodSecurityPolicy 自 Kubernetes v1.21 起已弃用,并将在 v1.25 中删除。
|
PodSecurityPolicy 自 Kubernetes v1.21 起已弃用,并将在 v1.25 中删除。
|
||||||
我们建议迁移到 [Pod 安全准入](/zh/docs/concepts/security/pod-security-admission/)或第三方准入插件。
|
我们建议迁移到 [Pod 安全准入](/zh-cn/docs/concepts/security/pod-security-admission/)或第三方准入插件。
|
||||||
|
|
||||||
|
|
|
@ -2,7 +2,7 @@
|
||||||
title: 抢占(Preemption)
|
title: 抢占(Preemption)
|
||||||
id: preemption
|
id: preemption
|
||||||
date: 2019-01-31
|
date: 2019-01-31
|
||||||
full_link: /zh/docs/concepts/scheduling-eviction/pod-priority-preemption/#preemption
|
full_link: /zh-cn/docs/concepts/scheduling-eviction/pod-priority-preemption/#preemption
|
||||||
short_description: >
|
short_description: >
|
||||||
Kubernetes 中的抢占逻辑通过驱逐节点上的低优先级 Pod 来帮助悬决的
|
Kubernetes 中的抢占逻辑通过驱逐节点上的低优先级 Pod 来帮助悬决的
|
||||||
Pod 找到合适的节点。
|
Pod 找到合适的节点。
|
||||||
|
@ -37,6 +37,6 @@ Kubernetes 中的抢占逻辑通过驱逐{{< glossary_tooltip term_id="node" >}}
|
||||||
If a Pod cannot be scheduled, the scheduler tries to [preempt](/docs/concepts/scheduling-eviction/pod-priority-preemption/#preemption) lower priority Pods to make scheduling of the pending Pod possible.
|
If a Pod cannot be scheduled, the scheduler tries to [preempt](/docs/concepts/scheduling-eviction/pod-priority-preemption/#preemption) lower priority Pods to make scheduling of the pending Pod possible.
|
||||||
-->
|
-->
|
||||||
如果一个 Pod 无法调度,调度器会尝试
|
如果一个 Pod 无法调度,调度器会尝试
|
||||||
[抢占](/zh/docs/concepts/scheduling-eviction/pod-priority-preemption/#preemption)
|
[抢占](/zh-cn/docs/concepts/scheduling-eviction/pod-priority-preemption/#preemption)
|
||||||
较低优先级的 Pod,以使得悬决的 Pod 有可能被调度。
|
较低优先级的 Pod,以使得悬决的 Pod 有可能被调度。
|
||||||
|
|
||||||
|
|
|
@ -43,7 +43,7 @@ actual server's reply to the client.
|
||||||
network proxy that runs on each node in your cluster, implementing part of
|
network proxy that runs on each node in your cluster, implementing part of
|
||||||
the Kubernetes {{< glossary_tooltip term_id="service">}} concept.
|
the Kubernetes {{< glossary_tooltip term_id="service">}} concept.
|
||||||
-->
|
-->
|
||||||
[kube-proxy](/zh/docs/reference/command-line-tools-reference/kube-proxy/) 是集群中每个节点上运行的网络代理,实现了部分 Kubernetes {{< glossary_tooltip term_id="service">}} 概念。
|
[kube-proxy](/zh-cn/docs/reference/command-line-tools-reference/kube-proxy/) 是集群中每个节点上运行的网络代理,实现了部分 Kubernetes {{< glossary_tooltip term_id="service">}} 概念。
|
||||||
|
|
||||||
<!--
|
<!--
|
||||||
You can run kube-proxy as a plain userland proxy service. If your operating
|
You can run kube-proxy as a plain userland proxy service. If your operating
|
||||||
|
|
|
@ -2,7 +2,7 @@
|
||||||
title: 基于角色的访问控制(RBAC)
|
title: 基于角色的访问控制(RBAC)
|
||||||
id: rbac
|
id: rbac
|
||||||
date: 2018-04-12
|
date: 2018-04-12
|
||||||
full_link: /zh/docs/reference/access-authn-authz/rbac/
|
full_link: /zh-cn/docs/reference/access-authn-authz/rbac/
|
||||||
short_description: >
|
short_description: >
|
||||||
管理授权决策,允许管理员通过 Kubernetes API 动态配置访问策略。
|
管理授权决策,允许管理员通过 Kubernetes API 动态配置访问策略。
|
||||||
|
|
||||||
|
@ -17,7 +17,7 @@ tags:
|
||||||
title: RBAC (Role-Based Access Control)
|
title: RBAC (Role-Based Access Control)
|
||||||
id: rbac
|
id: rbac
|
||||||
date: 2018-04-12
|
date: 2018-04-12
|
||||||
full_link: /zh/docs/reference/access-authn-authz/rbac/
|
full_link: /zh-cn/docs/reference/access-authn-authz/rbac/
|
||||||
short_description: >
|
short_description: >
|
||||||
Manages authorization decisions, allowing admins to dynamically configure access policies through the Kubernetes API.
|
Manages authorization decisions, allowing admins to dynamically configure access policies through the Kubernetes API.
|
||||||
|
|
||||||
|
|
|
@ -2,7 +2,7 @@
|
||||||
title: ReplicaSet
|
title: ReplicaSet
|
||||||
id: replica-set
|
id: replica-set
|
||||||
date: 2018-04-12
|
date: 2018-04-12
|
||||||
full_link: /zh/docs/concepts/workloads/controllers/replicaset/
|
full_link: /zh-cn/docs/concepts/workloads/controllers/replicaset/
|
||||||
short_description: >
|
short_description: >
|
||||||
ReplicaSet 是下一代副本控制器。
|
ReplicaSet 是下一代副本控制器。
|
||||||
|
|
||||||
|
@ -18,7 +18,7 @@ tags:
|
||||||
title: ReplicaSet
|
title: ReplicaSet
|
||||||
id: replica-set
|
id: replica-set
|
||||||
date: 2018-04-12
|
date: 2018-04-12
|
||||||
full_link: /zh/docs/concepts/workloads/controllers/replicaset/
|
full_link: /zh-cn/docs/concepts/workloads/controllers/replicaset/
|
||||||
short_description: >
|
short_description: >
|
||||||
ReplicaSet is the next-generation Replication Controller.
|
ReplicaSet is the next-generation Replication Controller.
|
||||||
|
|
||||||
|
|
|
@ -2,7 +2,7 @@
|
||||||
title: 资源配额(Resource Quotas)
|
title: 资源配额(Resource Quotas)
|
||||||
id: resource-quota
|
id: resource-quota
|
||||||
date: 2018-04-12
|
date: 2018-04-12
|
||||||
full_link: /zh/docs/concepts/policy/resource-quotas/
|
full_link: /zh-cn/docs/concepts/policy/resource-quotas/
|
||||||
short_description: >
|
short_description: >
|
||||||
资源配额提供了限制每个命名空间的资源消耗总和的约束。
|
资源配额提供了限制每个命名空间的资源消耗总和的约束。
|
||||||
|
|
||||||
|
@ -18,7 +18,7 @@ tags:
|
||||||
title: Resource Quotas
|
title: Resource Quotas
|
||||||
id: resource-quota
|
id: resource-quota
|
||||||
date: 2018-04-12
|
date: 2018-04-12
|
||||||
full_link: /zh/docs/concepts/policy/resource-quotas/
|
full_link: /zh-cn/docs/concepts/policy/resource-quotas/
|
||||||
short_description: >
|
short_description: >
|
||||||
Provides constraints that limit aggregate resource consumption per namespace.
|
Provides constraints that limit aggregate resource consumption per namespace.
|
||||||
|
|
||||||
|
|
|
@ -2,7 +2,7 @@
|
||||||
title: Secret
|
title: Secret
|
||||||
id: secret
|
id: secret
|
||||||
date: 2018-04-12
|
date: 2018-04-12
|
||||||
full_link: /zh/docs/concepts/configuration/secret/
|
full_link: /zh-cn/docs/concepts/configuration/secret/
|
||||||
short_description: >
|
short_description: >
|
||||||
Secret 用于存储敏感信息,如密码、 OAuth 令牌和 SSH 密钥。
|
Secret 用于存储敏感信息,如密码、 OAuth 令牌和 SSH 密钥。
|
||||||
|
|
||||||
|
@ -42,6 +42,6 @@ Allows for more control over how sensitive information is used and reduces the r
|
||||||
|
|
||||||
Secret 允许用户对如何使用敏感信息进行更多的控制,并减少信息意外暴露的风险。
|
Secret 允许用户对如何使用敏感信息进行更多的控制,并减少信息意外暴露的风险。
|
||||||
默认情况下,Secret 值被编码为 base64 字符串并以非加密的形式存储,但可以配置为
|
默认情况下,Secret 值被编码为 base64 字符串并以非加密的形式存储,但可以配置为
|
||||||
[静态加密(Encrypt at rest)](/zh/docs/tasks/administer-cluster/encrypt-data/#ensure-all-secrets-are-encrypted)。
|
[静态加密(Encrypt at rest)](/zh-cn/docs/tasks/administer-cluster/encrypt-data/#ensure-all-secrets-are-encrypted)。
|
||||||
{{< glossary_tooltip text="Pod" term_id="pod" >}} 通过挂载卷中的文件的方式引用 Secret,或者通过 kubelet 为 pod 拉取镜像时引用。
|
{{< glossary_tooltip text="Pod" term_id="pod" >}} 通过挂载卷中的文件的方式引用 Secret,或者通过 kubelet 为 pod 拉取镜像时引用。
|
||||||
Secret 非常适合机密数据使用,而 [ConfigMaps](/zh/docs/tasks/configure-pod-container/configure-pod-configmap/) 适用于非机密数据。
|
Secret 非常适合机密数据使用,而 [ConfigMaps](/zh-cn/docs/tasks/configure-pod-container/configure-pod-configmap/) 适用于非机密数据。
|
||||||
|
|
|
@ -2,7 +2,7 @@
|
||||||
title: 安全上下文(Security Context)
|
title: 安全上下文(Security Context)
|
||||||
id: security-context
|
id: security-context
|
||||||
date: 2018-04-12
|
date: 2018-04-12
|
||||||
full_link: /zh/docs/tasks/configure-pod-container/security-context/
|
full_link: /zh-cn/docs/tasks/configure-pod-container/security-context/
|
||||||
short_description: >
|
short_description: >
|
||||||
securityContext 字段定义 Pod 或容器的特权和访问控制设置,包括运行时 UID 和 GID。
|
securityContext 字段定义 Pod 或容器的特权和访问控制设置,包括运行时 UID 和 GID。
|
||||||
|
|
||||||
|
|
|
@ -2,7 +2,7 @@
|
||||||
title: 选择算符(Selector)
|
title: 选择算符(Selector)
|
||||||
id: selector
|
id: selector
|
||||||
date: 2018-04-12
|
date: 2018-04-12
|
||||||
full_link: /zh/docs/concepts/overview/working-with-objects/labels/
|
full_link: /zh-cn/docs/concepts/overview/working-with-objects/labels/
|
||||||
short_description: >
|
short_description: >
|
||||||
选择算符允许用户通过标签对一组资源对象进行筛选过滤。
|
选择算符允许用户通过标签对一组资源对象进行筛选过滤。
|
||||||
|
|
||||||
|
|
|
@ -2,7 +2,7 @@
|
||||||
title: ServiceAccount
|
title: ServiceAccount
|
||||||
id: service-account
|
id: service-account
|
||||||
date: 2018-04-12
|
date: 2018-04-12
|
||||||
full_link: /zh/docs/tasks/configure-pod-container/configure-service-account/
|
full_link: /zh-cn/docs/tasks/configure-pod-container/configure-service-account/
|
||||||
short_description: >
|
short_description: >
|
||||||
为在 Pod 中运行的进程提供标识。
|
为在 Pod 中运行的进程提供标识。
|
||||||
|
|
||||||
|
|
|
@ -44,4 +44,4 @@ list, provision, and bind with Managed Services offered by Service Brokers.
|
||||||
{{< glossary_tooltip text="服务代理(Service Brokers)" term_id="service-broker">}}会实现
|
{{< glossary_tooltip text="服务代理(Service Brokers)" term_id="service-broker">}}会实现
|
||||||
[开放服务代理 API 规范](https://github.com/openservicebrokerapi/servicebroker/blob/v2.13/spec.md)
|
[开放服务代理 API 规范](https://github.com/openservicebrokerapi/servicebroker/blob/v2.13/spec.md)
|
||||||
并为应用提供使用其托管服务的标准接口。
|
并为应用提供使用其托管服务的标准接口。
|
||||||
[服务目录(Service Catalog)](/zh/docs/concepts/extend-kubernetes/service-catalog/)则提供一种方法,用来列举、供应和绑定服务代理商所提供的托管服务。
|
[服务目录(Service Catalog)](/zh-cn/docs/concepts/extend-kubernetes/service-catalog/)则提供一种方法,用来列举、供应和绑定服务代理商所提供的托管服务。
|
||||||
|
|
|
@ -2,7 +2,7 @@
|
||||||
title: 服务(Service)
|
title: 服务(Service)
|
||||||
id: service
|
id: service
|
||||||
date: 2018-04-12
|
date: 2018-04-12
|
||||||
full_link: /zh/docs/concepts/services-networking/service/
|
full_link: /zh-cn/docs/concepts/services-networking/service/
|
||||||
short_description: >
|
short_description: >
|
||||||
将运行在一组 Pods 上的应用程序公开为网络服务的抽象方法。
|
将运行在一组 Pods 上的应用程序公开为网络服务的抽象方法。
|
||||||
|
|
||||||
|
|
|
@ -2,7 +2,7 @@
|
||||||
title: StatefulSet
|
title: StatefulSet
|
||||||
id: statefulset
|
id: statefulset
|
||||||
date: 2018-04-12
|
date: 2018-04-12
|
||||||
full_link: /zh/docs/concepts/workloads/controllers/statefulset/
|
full_link: /zh-cn/docs/concepts/workloads/controllers/statefulset/
|
||||||
short_description: >
|
short_description: >
|
||||||
StatefulSet 用来管理某 Pod 集合的部署和扩缩,并为这些 Pod 提供持久存储和持久标识符。
|
StatefulSet 用来管理某 Pod 集合的部署和扩缩,并为这些 Pod 提供持久存储和持久标识符。
|
||||||
aka:
|
aka:
|
||||||
|
|
|
@ -2,7 +2,7 @@
|
||||||
title: 静态 Pod(Static Pod)
|
title: 静态 Pod(Static Pod)
|
||||||
id: static-pod
|
id: static-pod
|
||||||
date: 2019-02-12
|
date: 2019-02-12
|
||||||
full_link: /zh/docs/tasks/configure-pod-container/static-pod/
|
full_link: /zh-cn/docs/tasks/configure-pod-container/static-pod/
|
||||||
short_description: >
|
short_description: >
|
||||||
静态Pod(Static Pod)是指由特定节点上的 kubelet 守护进程直接管理的 Pod。
|
静态Pod(Static Pod)是指由特定节点上的 kubelet 守护进程直接管理的 Pod。
|
||||||
|
|
||||||
|
|
|
@ -2,7 +2,7 @@
|
||||||
title: StorageClass
|
title: StorageClass
|
||||||
id: storageclass
|
id: storageclass
|
||||||
date: 2018-04-12
|
date: 2018-04-12
|
||||||
full_link: /zh/docs/concepts/storage/storage-classes/
|
full_link: /zh-cn/docs/concepts/storage/storage-classes/
|
||||||
short_description: >
|
short_description: >
|
||||||
StorageClass 是管理员用来描述可用的不同存储类型的一种方法。
|
StorageClass 是管理员用来描述可用的不同存储类型的一种方法。
|
||||||
|
|
||||||
|
|
|
@ -2,7 +2,7 @@
|
||||||
title: sysctl
|
title: sysctl
|
||||||
id: sysctl
|
id: sysctl
|
||||||
date: 2019-02-12
|
date: 2019-02-12
|
||||||
full_link: /zh/docs/tasks/administer-cluster/sysctl-cluster/
|
full_link: /zh-cn/docs/tasks/administer-cluster/sysctl-cluster/
|
||||||
short_description: >
|
short_description: >
|
||||||
用于获取和设置 Unix 内核参数的接口
|
用于获取和设置 Unix 内核参数的接口
|
||||||
|
|
||||||
|
|
|
@ -2,7 +2,7 @@
|
||||||
title: 污点(Taint)
|
title: 污点(Taint)
|
||||||
id: taint
|
id: taint
|
||||||
date: 2019-01-11
|
date: 2019-01-11
|
||||||
full_link: /zh/docs/concepts/scheduling-eviction/taint-and-toleration/
|
full_link: /zh-cn/docs/concepts/scheduling-eviction/taint-and-toleration/
|
||||||
short_description: >
|
short_description: >
|
||||||
污点是一种一个核心对象,包含三个必需的属性:key、value 和 effect。
|
污点是一种一个核心对象,包含三个必需的属性:key、value 和 effect。
|
||||||
污点会阻止在节点或节点组上调度 Pod。
|
污点会阻止在节点或节点组上调度 Pod。
|
||||||
|
|
|
@ -2,7 +2,7 @@
|
||||||
title: 容忍度(Toleration)
|
title: 容忍度(Toleration)
|
||||||
id: toleration
|
id: toleration
|
||||||
date: 2019-01-11
|
date: 2019-01-11
|
||||||
full_link: /zh/docs/concepts/scheduling-eviction/taint-and-toleration/
|
full_link: /zh-cn/docs/concepts/scheduling-eviction/taint-and-toleration/
|
||||||
short_description: >
|
short_description: >
|
||||||
一个核心对象,由三个必需的属性组成:key、value 和 effect。
|
一个核心对象,由三个必需的属性组成:key、value 和 effect。
|
||||||
容忍度允许将 Pod 调度到具有对应污点的节点或节点组上。
|
容忍度允许将 Pod 调度到具有对应污点的节点或节点组上。
|
||||||
|
|
|
@ -2,7 +2,7 @@
|
||||||
title: UID
|
title: UID
|
||||||
id: uid
|
id: uid
|
||||||
date: 2018-04-12
|
date: 2018-04-12
|
||||||
full_link: /zh/docs/concepts/overview/working-with-objects/names/
|
full_link: /zh-cn/docs/concepts/overview/working-with-objects/names/
|
||||||
short_description: >
|
short_description: >
|
||||||
由 Kubernetes 系统生成、用来唯一标识对象的字符串。
|
由 Kubernetes 系统生成、用来唯一标识对象的字符串。
|
||||||
|
|
||||||
|
|
|
@ -2,7 +2,7 @@
|
||||||
title: 卷(Volume)
|
title: 卷(Volume)
|
||||||
id: volume
|
id: volume
|
||||||
date: 2018-04-12
|
date: 2018-04-12
|
||||||
full_link: /zh/docs/concepts/storage/volumes/
|
full_link: /zh-cn/docs/concepts/storage/volumes/
|
||||||
short_description: >
|
short_description: >
|
||||||
包含可被 Pod 中容器访问的数据的目录。
|
包含可被 Pod 中容器访问的数据的目录。
|
||||||
|
|
||||||
|
@ -47,4 +47,4 @@ A Kubernetes volume lives as long as the Pod that encloses it. Consequently, a v
|
||||||
<!--
|
<!--
|
||||||
See [storage](/docs/concepts/storage/) for more information.
|
See [storage](/docs/concepts/storage/) for more information.
|
||||||
-->
|
-->
|
||||||
更多信息可参考[storage](/zh/docs/concepts/storage/)
|
更多信息可参考[storage](/zh-cn/docs/concepts/storage/)
|
|
@ -2,7 +2,7 @@
|
||||||
title: 工作负载(Workload)
|
title: 工作负载(Workload)
|
||||||
id: workloads
|
id: workloads
|
||||||
date: 2019-02-13
|
date: 2019-02-13
|
||||||
full_link: /zh/docs/concepts/workloads/
|
full_link: /zh-cn/docs/concepts/workloads/
|
||||||
short_description: >
|
short_description: >
|
||||||
工作负载是在 Kubernetes 上运行的应用程序。
|
工作负载是在 Kubernetes 上运行的应用程序。
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue