add zh pages

This commit is contained in:
Karen Bradshaw
2020-06-01 09:23:39 -04:00
parent 21fd0a12f9
commit 4b35d4d401
303 changed files with 2764 additions and 2439 deletions
@@ -1,6 +1,6 @@
---
title: 干扰
content_template: templates/concept
content_type: concept
weight: 60
---
@@ -11,12 +11,12 @@ reviewers:
- foxish
- davidopp
title: Disruptions
content_template: templates/concept
content_type: concept
weight: 60
---
-->
{{% capture overview %}}
<!-- overview -->
<!--
This guide is for application owners who want to build
highly available applications, and thus need to understand
@@ -32,10 +32,10 @@ cluster actions, like upgrading and autoscaling clusters.
文档同样适用于想要执行自动化集群操作(例如升级和自动扩展集群)的集群管理员。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
<!--
## Voluntary and Involuntary Disruptions
@@ -511,10 +511,11 @@ the nodes in your cluster, such as a node or system software upgrade, here are s
- 编写可容忍干扰的应用程序是棘手的,但对于支持容忍自愿干扰所做的工作,和支持自动扩缩和容忍非
愿干扰所做工作相比,有大量的重叠
{{% /capture %}}
{{% capture whatsnext %}}
## {{% heading "whatsnext" %}}
<!--
* Follow steps to protect your application by [configuring a Pod Disruption Budget](/docs/tasks/run-application/configure-pdb/).
@@ -529,4 +530,4 @@ the nodes in your cluster, such as a node or system software upgrade, here are s
* 了解更多关于[排空节点](/docs/tasks/administer-cluster/safely-drain-node/)的信息。
{{% /capture %}}
@@ -1,6 +1,6 @@
---
title: 临时容器
content_template: templates/concept
content_type: concept
weight: 80
---
@@ -10,12 +10,12 @@ reviewers:
- verb
- yujuhong
title: Ephemeral Containers
content_template: templates/concept
content_type: concept
weight: 80
---
-->
{{% capture overview %}}
<!-- overview -->
{{< feature-state state="alpha" for_k8s_version="v1.16" >}}
@@ -40,9 +40,9 @@ feature could change significantly in the future or be removed entirely.
临时容器处于早期的 alpha 阶段,不适用于生产环境集群。应该预料到临时容器在某些情况下不起作用,例如在定位容器的命名空间时。根据 [Kubernetes 弃用政策](/docs/reference/using-api/deprecation-policy/),该 alpha 功能将来可能发生重大变化或完全删除。
{{< /warning >}}
{{% /capture %}}
{{% capture body %}}
<!-- body -->
<!--
## Understanding ephemeral containers
@@ -321,4 +321,4 @@ PID USER TIME COMMAND
29 root 0:00 ps auxww
```
{{% /capture %}}
@@ -2,10 +2,10 @@
approvers:
- erictune
title: Init 容器
content_template: templates/concept
content_type: concept
---
{{% capture overview %}}
<!-- overview -->
<!--
This page provides an overview of init containers: specialized containers that run before app containers in a {{< glossary_tooltip text="Pod" term_id="pod" >}}.
@@ -13,14 +13,14 @@ Init containers can contain utilities or setup scripts not present in an app ima
-->
本页提供了 Init 容器的概览,它是一种专用的容器,在{{< glossary_tooltip text="Pod" term_id="pod" >}}内的应用容器启动之前运行,并包括一些应用镜像中不存在的实用工具和安装脚本。
{{% /capture %}}
<!--
You can specify init containers in the Pod specification alongside the `containers` array (which describes app containers).
-->
你可以在Pod的规格信息中与containers数组同级的位置指定 Init 容器。
{{% capture body %}}
<!-- body -->
<!--
@@ -432,10 +432,11 @@ Pod重启导致 Init 容器重新执行,主要有如下几个原因:
* 当 `restartPolicy` 设置为 Always,Pod 中所有容器会终止而强制重启,由于垃圾收集导致 Init 容器的完成记录丢失。
{{% /capture %}}
{{% capture whatsnext %}}
## {{% heading "whatsnext" %}}
<!--
* Read about [creating a Pod that has an init container](/docs/tasks/configure-pod-container/configure-pod-initialization/#create-a-pod-that-has-an-init-container)
@@ -444,4 +445,4 @@ Pod重启导致 Init 容器重新执行,主要有如下几个原因:
* 阅读[创建包含 Init 容器的 Pod](/docs/tasks/configure-pod-container/configure-pod-initialization/#create-a-pod-that-has-an-init-container)
* 学习如何[调测 Init 容器](/docs/tasks/debug-application-cluster/debug-init-containers/)
{{% /capture %}}
@@ -1,18 +1,18 @@
---
title: Pod 的生命周期
content_template: templates/concept
content_type: concept
---
{{% capture overview %}}
<!-- overview -->
{{< comment >}}Updated: 4/14/2015{{< /comment >}}
{{< comment >}}Edited and moved to Concepts section: 2/2/17{{< /comment >}}
该页面将描述 Pod 的生命周期。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
## Pod phase
@@ -174,7 +174,7 @@ spec:
- 节点控制器将 Pod `phase` 设置为 Failed。
- 如果是用控制器来运行,Pod 将在别处重建。
{{% /capture %}}
@@ -1,6 +1,6 @@
---
title: Pod 概览
content_template: templates/concept
content_type: concept
weight: 10
card:
name: 概念
@@ -12,7 +12,7 @@ card:
reviewers:
- erictune
title: Pod Overview
content_template: templates/concept
content_type: concept
weight: 10
card:
name: concepts
@@ -23,12 +23,12 @@ card:
<!--
This page provides an overview of `Pod`, the smallest deployable object in the Kubernetes object model.
-->
{{% capture overview %}}
<!-- overview -->
本节提供了 `Pod` 的概览信息,`Pod` 是最小可部署的 Kubernetes 对象模型。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
<!--
## Understanding Pods
@@ -248,7 +248,7 @@ Pod 模板就像饼干切割器,而不是指定所有副本的当前期望状
这与 Pod 形成有意的对比,Pod 指定了属于 Pod 的所有容器的当前期望状态。
这种方法从根本上简化了系统语义,增加了原语的灵活性。
{{% /capture %}}
<!--
* Learn more about [Pods](/docs/concepts/workloads/pods/pod/)
@@ -256,9 +256,10 @@ Pod 模板就像饼干切割器,而不是指定所有副本的当前期望状
* [Pod Termination](/docs/concepts/workloads/pods/pod/#termination-of-pods)
* [Pod Lifecycle](/docs/concepts/workloads/pods/pod-lifecycle/)
-->
{{% capture whatsnext %}}
## {{% heading "whatsnext" %}}
* 详细了解 [Pod](/docs/concepts/workloads/pods/pod/)
* 了解有关 Pod 行为的更多信息:
* [Pod 的终止](/docs/concepts/workloads/pods/pod/#termination-of-pods)
* [Pod 的生命周期](/docs/concepts/workloads/pods/pod-lifecycle/)
{{% /capture %}}
@@ -1,20 +1,20 @@
---
title: Pod 拓扑扩展约束
content_template: templates/concept
content_type: concept
weight: 50
---
<!--
title: Pod Topology Spread Constraints
content_template: templates/concept
content_type: concept
weight: 50
---
-->
{{% capture overview %}}
<!-- overview -->
{{< feature-state for_k8s_version="v1.16" state="alpha" >}}
@@ -24,9 +24,9 @@ You can use _topology spread constraints_ to control how {{< glossary_tooltip te
可以使用*拓扑扩展约束*来控制 {{< glossary_tooltip text="Pods" term_id="Pod" >}} 在集群内故障域(例如地区,区域,节点和其他用户自定义拓扑域)之间的分布。这可以帮助实现高可用以及提升资源利用率。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
<!--
## Prerequisites
@@ -399,4 +399,4 @@ As of 1.16, at which this feature is Alpha, there are some known limitations:
- `Deployment` 的缩容可能导致 pod 分布不平衡。
- pod 匹配到污点节点是允许的。参考 [Issue 80921](https://github.com/kubernetes/kubernetes/issues/80921)。
{{% /capture %}}
@@ -1,17 +1,17 @@
---
title: Pods
content_template: templates/concept
content_type: concept
weight: 20
---
<!--
reviewers:
title: Pods
content_template: templates/concept
content_type: concept
weight: 20
-->
{{% capture overview %}}
<!-- overview -->
<!--
_Pods_ are the smallest deployable units of computing that can be created and
@@ -20,10 +20,10 @@ managed in Kubernetes.
_Pod_ 是可以在 Kubernetes 中创建和管理的、最小的可部署的计算单元。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
<!--
## What is a Pod?
@@ -384,4 +384,4 @@ describes the object in detail.
Pod 是 Kubernetes REST API 中的顶级资源。
[Pod API 对象](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#pod-v1-core)定义详细描述了该 Pod 对象。
{{% /capture %}}
@@ -1,6 +1,6 @@
---
title: Pod Preset
content_template: templates/concept
content_type: concept
weight: 50
---
@@ -9,7 +9,7 @@ weight: 50
reviewers:
- jessfraz
title: Pod Preset
content_template: templates/concept
content_type: concept
weight: 50
---
-->
@@ -19,12 +19,12 @@ This page provides an overview of PodPresets, which are objects for injecting
certain information into pods at creation time. The information can include
secrets, volumes, volume mounts, and environment variables.
-->
{{% capture overview %}}
<!-- overview -->
本文提供了 PodPreset 的概述。 在 Pod 创建时,用户可以使用 PodPreset 对象将特定信息注入 Pod 中,这些信息可以包括 secret、 卷、卷挂载和环境变量。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
<!--
## Understanding Pod Presets
@@ -164,12 +164,13 @@ In order to use Pod Presets in your cluster you must ensure the following:
1. 已经通过在相应的命名空间中创建 `PodPreset` 对象,定义了 Pod Preset。
{{% /capture %}}
{{% capture whatsnext %}}
## {{% heading "whatsnext" %}}
<!--
* [Injecting data into a Pod using PodPreset](/docs/tasks/inject-data-application/podpreset/)
-->
* [使用 PodPreset 将信息注入 Pod](/docs/tasks/inject-data-application/podpreset/)
{{% /capture %}}