[zh-cn] Sync some glossary pages
Sean Wei
parent
68aa2e12bd
commit
37107cdd81
|
|
@ -26,7 +26,8 @@ tags:
|
|||
<!--
|
||||
CIDR (Classless Inter-Domain Routing) is a notation for describing blocks of IP addresses and is used heavily in various networking configurations.
|
||||
-->
|
||||
CIDR （无类域间路由（Classless Inter-Domain Routing））是一种描述 IP 地址块的符号，被广泛使用于各种网络配置中。
|
||||
CIDR（无类域间路由，Classless Inter-Domain Routing）是一种描述
|
||||
IP 地址块的符号，被广泛使用于各种网络配置中。
|
||||
|
||||
<!--more-->
|
||||
|
||||
|
|
|
|||
|
|
@ -38,7 +38,7 @@ kops 是一个命令行工具，可以帮助你创建、销毁、升级和维护
|
|||
kops has general availability support only for AWS.
|
||||
Support for using kops with GCE and VMware vSphere are in alpha.
|
||||
-->
|
||||
注意：官方仅支持 AWS。对 GCE 和 VMware vSphere 的支持还处于 Alpha 阶段。
|
||||
官方仅支持 AWS。对 GCE 和 VMware vSphere 的支持还处于 Alpha 阶段。
|
||||
{{< /note >}}
|
||||
|
||||
<!--
|
||||
|
|
|
|||
|
|
@ -4,13 +4,12 @@ id: object
|
|||
date: 2020-10-12
|
||||
full_link: /zh-cn/docs/concepts/overview/working-with-objects/kubernetes-objects/#kubernetes-objects
|
||||
short_description: >
|
||||
Kubernetes 系统中的实体, 代表了集群的部分状态。
|
||||
Kubernetes 系统中的实体，代表了集群的部分状态。
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
<!--
|
||||
---
|
||||
title: Object
|
||||
id: object
|
||||
date: 2020-10-12
|
||||
|
|
@ -20,8 +19,8 @@ short_description: >
|
|||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
An entity in the Kubernetes system. The Kubernetes API uses these entities to represent the state
|
||||
of your cluster.
|
||||
|
|
|
|||
|
|
@ -1,10 +1,10 @@
|
|||
---
|
||||
id: pod-disruption
|
||||
title: Pod 干扰
|
||||
full_link: /docs/concepts/workloads/pods/disruptions/
|
||||
full_link: /zh-cn/docs/concepts/workloads/pods/disruptions/
|
||||
date: 2021-05-12
|
||||
short_description: >
|
||||
自愿或非自愿地终止节点上的 pod 的过程.
|
||||
自愿或非自愿地终止节点上的 Pod 的过程。
|
||||
|
||||
aka:
|
||||
related:
|
||||
|
|
@ -13,9 +13,7 @@ related:
|
|||
tags:
|
||||
- operation
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
id: pod-disruption
|
||||
title: Pod Disruption
|
||||
full_link: /docs/concepts/workloads/pods/disruptions/
|
||||
|
|
@ -29,15 +27,14 @@ related:
|
|||
- container
|
||||
tags:
|
||||
- operation
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
[Pod disruption](/docs/concepts/workloads/pods/disruptions/) is the process by which
|
||||
Pods on Nodes are terminated either voluntarily or involuntarily.
|
||||
-->
|
||||
|
||||
[pod 干扰](/zh-cn/docs/concepts/workloads/pods/disruptions/) 是指节点上的 pod 被自愿或非自愿终止的过程。
|
||||
[Pod 干扰](/zh-cn/docs/concepts/workloads/pods/disruptions/) 是指节点上的
|
||||
Pod 被自愿或非自愿终止的过程。
|
||||
|
||||
<!--more-->
|
||||
|
||||
|
|
@ -46,5 +43,5 @@ Voluntary disruptions are started intentionally by application owners or cluster
|
|||
administrators. Involuntary disruptions are unintentional and can be triggered by
|
||||
unavoidable issues like Nodes running out of resources, or by accidental deletions.
|
||||
-->
|
||||
|
||||
自愿干扰是由应用程序所有者或集群管理员有意启动的。非自愿干扰是无意的，可能由不可避免的问题触发，如节点耗尽资源或意外删除。
|
||||
自愿干扰是由应用程序所有者或集群管理员有意启动的。非自愿干扰是无意的，
|
||||
可能由不可避免的问题触发，如节点耗尽资源或意外删除。
|
||||
|
|
|
|||
|
|
@ -11,9 +11,7 @@ tags:
|
|||
- core-object
|
||||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Pod Security Policy
|
||||
id: pod-security-policy
|
||||
date: 2018-04-12
|
||||
|
|
@ -25,7 +23,6 @@ aka:
|
|||
tags:
|
||||
- core-object
|
||||
- fundamental
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
|
|
@ -41,11 +38,12 @@ A cluster-level resource that controls security sensitive aspects of the Pod spe
|
|||
-->
|
||||
|
||||
Pod 安全策略是集群级别的资源，它控制着 Pod 规约中的安全性敏感的内容。
|
||||
`PodSecurityPolicy`对象定义了一组条件以及相关字段的默认值，Pod 运行时必须满足这些条件。Pod 安全策略控制实现上体现为一个可选的准入控制器。
|
||||
`PodSecurityPolicy` 对象定义了一组条件以及相关字段的默认值，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 was deprecated as of Kubernetes v1.21, and removed in v1.25.
|
||||
As an alternative, use [Pod Security Admission](/docs/concepts/security/pod-security-admission/), or a 3rd party admission plugin.
|
||||
-->
|
||||
PodSecurityPolicy 自 Kubernetes v1.21 起已弃用，并将在 v1.25 中删除。
|
||||
我们建议迁移到 [Pod 安全准入](/zh-cn/docs/concepts/security/pod-security-admission/)或第三方准入插件。
|
||||
|
||||
PodSecurityPolicy 已于 Kubernetes v1.21 起弃用，并在 v1.25 中删除。
|
||||
作为替代方案，请使用 [Pod 安全准入](/zh-cn/docs/concepts/security/pod-security-admission/)或第三方准入插件。
|
||||
|
|
|
|||
|
|
@ -12,13 +12,11 @@ tags:
|
|||
- operation
|
||||
- architecture
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Resource Quotas
|
||||
id: resource-quota
|
||||
date: 2018-04-12
|
||||
full_link: /zh-cn/docs/concepts/policy/resource-quotas/
|
||||
full_link: /docs/concepts/policy/resource-quotas/
|
||||
short_description: >
|
||||
Provides constraints that limit aggregate resource consumption per namespace.
|
||||
|
||||
|
|
@ -27,13 +25,11 @@ tags:
|
|||
- fundamental
|
||||
- operation
|
||||
- architecture
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
Provides constraints that limit aggregate resource consumption per {{< glossary_tooltip term_id="namespace" >}}.
|
||||
-->
|
||||
|
||||
资源配额提供了限制每个 {{< glossary_tooltip text="命名空间" term_id="namespace">}} 的资源消耗总和的约束。
|
||||
|
||||
<!--more-->
|
||||
|
|
@ -41,7 +37,4 @@ tags:
|
|||
<!--
|
||||
Limits the quantity of objects that can be created in a namespace by type, as well as the total amount of compute resources that may be consumed by resources in that project.
|
||||
-->
|
||||
|
||||
限制了命名空间中每种对象可以创建的数量，也限制了项目中可被资源对象利用的计算资源总数。
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -10,9 +10,7 @@ aka:
|
|||
tags:
|
||||
- community
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Upstream (disambiguation)
|
||||
id: upstream
|
||||
date: 2018-04-12
|
||||
|
|
@ -23,7 +21,6 @@ short_description: >
|
|||
aka:
|
||||
tags:
|
||||
- community
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
|
|
@ -38,5 +35,8 @@ tags:
|
|||
* In **GitHub** or **git**: The convention is to refer to a source repo as *upstream*, whereas the forked repo is considered *downstream*.
|
||||
-->
|
||||
|
||||
* 在 **Kubernetes社区**：对话中通常使用 *upstream* 来表示核心 Kubernetes 代码库，也就是更广泛的 kubernetes 生态系统、其他代码或第三方工具所依赖的仓库。 例如，[社区成员](#term-member)可能会建议将某个功能特性贡献到 upstream，使其位于核心代码库中，而不是维护于插件或第三方工具中。
|
||||
* 在 **GitHub** 或 **git** 中：约定是将源仓库称为 *upstream*，而派生的仓库则被视为 *downstream*。
|
||||
* 在 **Kubernetes 社区**：对话中通常使用 *upstream* 来表示核心 Kubernetes
|
||||
代码库，也就是更广泛的 Kubernetes 生态系统、其他代码或第三方工具所依赖的仓库。
|
||||
例如，[社区成员](#term-member)可能会建议将某个功能特性贡献到 upstream，
|
||||
使其位于核心代码库中，而不是维护于插件或第三方工具中。
|
||||
* 在 **GitHub** 或 **git** 中：惯例是将源仓库称为 *upstream*，而派生的仓库则被视为 *downstream*。
|
||||
|
|
|
|||
|
|
@ -10,10 +10,7 @@ aka:
|
|||
tags:
|
||||
- fundamental
|
||||
---
|
||||
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Workload
|
||||
id: workloads
|
||||
date: 2019-02-13
|
||||
|
|
@ -24,7 +21,6 @@ short_description: >
|
|||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
|
|
@ -42,7 +38,8 @@ For example, a workload that has a web server and a database might run the
|
|||
database in one {{< glossary_tooltip term_id="StatefulSet" >}} and the web server
|
||||
in a {{< glossary_tooltip term_id="Deployment" >}}.
|
||||
-->
|
||||
代表不同类型或部分工作负载的各种核心对象包括 DaemonSet， Deployment， Job， ReplicaSet， and StatefulSet。
|
||||
代表不同类型或部分工作负载的各种核心对象包括 DaemonSet、Deployment、Job、ReplicaSet 和 StatefulSet。
|
||||
|
||||
例如，具有 Web 服务器和数据库的工作负载可能在一个 {{< glossary_tooltip term_id="StatefulSet" >}} 中运行数据库，
|
||||
例如，具有 Web 服务器和数据库的工作负载可能在一个
|
||||
{{< glossary_tooltip term_id="StatefulSet" >}} 中运行数据库，
|
||||
而 Web 服务器运行在 {{< glossary_tooltip term_id="Deployment" >}}。
|
||||
Loading…
Reference in New Issue