whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

add zh pages

Browse Source
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
Download Patch File Download Diff File Expand all files Collapse all files
content/zh/docs/concepts/workloads/controllers/cron-jobs.md
+7 -6
View File
@@ -1,6 +1,6 @@
---
title: CronJob
content_template: templates/concept
content_type: concept
weight: 80
---
@@ -11,12 +11,12 @@ reviewers:
- soltysh
- janetkuo
title: CronJob
content_template: templates/concept
content_type: concept
weight: 80
---
-->
{{% capture overview %}}
<!-- overview -->
{{< feature-state for_k8s_version="v1.8" state="beta" >}}
@@ -62,10 +62,10 @@ For instructions on creating and working with cron jobs, and for an example of a
有关创建和使用 CronJob 的说明及规范文件的示例，请参见[使用 CronJob 运行自动化任务](/docs/tasks/job/automated-tasks-with-cron-jobs)。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
<!--
## Cron Job Limitations
@@ -133,4 +133,5 @@ the Job in turn is responsible for the management of the Pods it represents.
-->
CronJob 仅负责创建与其调度时间相匹配的 Job，而 Job 又负责管理其代表的 Pod。
{{% /capture %}}
content/zh/docs/concepts/workloads/controllers/daemonset.md
+6 -6
View File
@@ -1,6 +1,6 @@
---
title: DaemonSet
content_template: templates/concept
content_type: concept
weight: 50
---
@@ -13,12 +13,12 @@ reviewers:
- janetkuo
- kow3ns
title: DaemonSet
content_template: templates/concept
content_type: concept
weight: 50
---
--->
{{% capture overview %}}
<!-- overview -->
<!--
A _DaemonSet_ ensures that all (or some) Nodes run a copy of a Pod. As nodes are added to the
@@ -51,10 +51,10 @@ different flags and/or different memory and cpu requests for different hardware
一个稍微复杂的用法是单独对每种 daemon 类型使用多个 DaemonSet，但具有不同的标志，
并且对不同硬件类型具有不同的内存、CPU 要求。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
<!--
## Writing a DaemonSet Spec
@@ -391,4 +391,4 @@ DaemonSet 与 [Deployments](/docs/concepts/workloads/controllers/deployment/)
为无状态的 Service 使用 Deployments，比如前端 Frontend 服务，实现对副本的数量进行扩缩容、平滑升级，比基于精确控制 Pod 运行在某个主机上要重要得多。
需要 Pod 副本总是运行在全部或特定主机上，并需要先于其他 Pod 启动，当这被认为非常重要时，应该使用 Daemon Controller。
{{% /capture %}}
content/zh/docs/concepts/workloads/controllers/deployment.md
+5 -5
View File
@@ -9,11 +9,11 @@ feature:
<!-- Kubernetes progressively rolls out changes to your application or its configuration, while monitoring application health to ensure it doesn't kill all your instances at the same time. If something goes wrong, Kubernetes will rollback the change for you. Take advantage of a growing ecosystem of deployment solutions. -->
Kubernetes 会逐步推出针对应用或其配置的更改，确保在监视应用程序运行状况的同时，不会终止所有实例。如果出现问题，Kubernetes 会为您回滚更改。充分利用不断成长的部署解决方案生态系统。
content_template: templates/concept
content_type: concept
weight: 30
---
{{% capture overview %}}
<!-- overview -->
<!--
@@ -40,9 +40,9 @@ Do not manage ReplicaSets owned by a Deployment. Consider opening an issue in th
{{< /note >}}
{{% /capture %}}
{{% capture body %}}
<!-- body -->
You describe a _desired state_ in a Deployment, and the Deployment controller changes the actual state to the desired state at a controlled rate. You can define Deployments to create new ReplicaSets, or to remove existing Deployments and adopt all their resources with new Deployments.
@@ -2197,4 +2197,4 @@ additional features, such as rolling back to any previous revision even after th
-->
[`kubectl rolling update`](/docs/reference/generated/kubectl/kubectl-commands#rolling-update)更新 Pods 和副本控制器的方式类似。但是，建议采取 Deployments 的方式来更新，因为它们是声明性的，在服务器端，并且具有其他功能，例如，即使在滚动更新完成后，也会回滚到以前的任何修改版本。
{{% /capture %}}
content/zh/docs/concepts/workloads/controllers/garbage-collection.md
+9 -8
View File
@@ -1,18 +1,18 @@
---
title: 垃圾收集
content_template: templates/concept
content_type: concept
weight: 60
---
<!--
---
title: Garbage Collection
content_template: templates/concept
content_type: concept
weight: 60
---
-->
{{% capture overview %}}
<!-- overview -->
<!--
The role of the Kubernetes garbage collector is to delete certain objects
@@ -21,10 +21,10 @@ that once had an owner, but no longer have an owner.
Kubernetes 垃圾收集器的作用是删除某些曾经拥有所有者（owner）但现在不再拥有所有者的对象。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
<!--
## Owners and dependents
@@ -288,10 +288,11 @@ Tracked at [#26120](https://github.com/kubernetes/kubernetes/issues/26120)
跟踪 [#26120](https://github.com/kubernetes/kubernetes/issues/26120)
{{% /capture %}}
{{% capture whatsnext %}}
## {{% heading "whatsnext" %}}
<!--
@@ -303,7 +304,7 @@ Tracked at [#26120](https://github.com/kubernetes/kubernetes/issues/26120)
[设计文档 2](https://git.k8s.io/community/contributors/design-proposals/api-machinery/synchronous-garbage-collection.md)
{{% /capture %}}
content/zh/docs/concepts/workloads/controllers/replicaset.md
+5 -5
View File
@@ -4,11 +4,11 @@ reviewers:
- bprashanth
- madhusudancs
title: ReplicaSet
content_template: templates/concept
content_type: concept
weight: 10
---
{{% capture overview %}}
<!-- overview -->
<!--
ReplicaSet is the next-generation Replication Controller. The only difference
@@ -21,9 +21,9 @@ whereas a Replication Controller only supports equality-based selector requireme
ReplicaSet 是下一代的 Replication Controller。 _ReplicaSet_ 和 [_Replication Controller_](/docs/concepts/workloads/controllers/replicationcontroller/) 的唯一区别是选择器的支持。ReplicaSet 支持新的基于集合的选择器需求，这在[标签用户指南](/docs/concepts/overview/working-with-objects/labels/#label-selectors)中有描述。而 Replication Controller 仅支持基于相等选择器的需求。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
<!--
## How to use a ReplicaSet
@@ -412,5 +412,5 @@ safe to terminate when the machine is otherwise ready to be rebooted/shutdown.
对于管理那些提供主机级别功能（如主机监控和主机日志）的容器，就要用[`DaemonSet`](/docs/concepts/workloads/controllers/daemonset/) 而不用 ReplicaSet。
这些 Pod 的寿命与主机寿命有关：这些 Pod 需要先于主机上的其他 Pod 运行，并且在机器准备重新启动/关闭时安全地终止。
{{% /capture %}}
content/zh/docs/concepts/workloads/controllers/replicationcontroller.md
+6 -6
View File
@@ -6,7 +6,7 @@ feature:
description: >
重新启动失败的容器，在节点死亡时替换并重新调度容器，杀死不响应用户定义的健康检查的容器，并且在它们准备好服务之前不会将它们公布给客户端。
content_template: templates/concept
content_type: concept
weight: 20
---
@@ -21,11 +21,11 @@ feature:
description: >
Restarts containers that fail, replaces and reschedules containers when nodes die, kills containers that don't respond to your user-defined health check, and doesn't advertise them to clients until they are ready to serve.
content_template: templates/concept
content_type: concept
weight: 20
-->
{{% capture overview %}}
<!-- overview -->
<!--
A [`Deployment`](/docs/concepts/workloads/controllers/deployment/) that configures a [`ReplicaSet`](/docs/concepts/workloads/controllers/replicaset/) is now the recommended way to set up replication.
@@ -41,10 +41,10 @@ always up and available.
-->
_ReplicationController_ 确保在任何时候都有特定数量的 pod 副本处于运行状态。
换句话说，ReplicationController 确保一个 pod 或一组同类的 pod 总是可用的。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
<!--
## How a ReplicationController Works
@@ -560,4 +560,4 @@ Read [Run Stateless AP Replication Controller](/docs/tutorials/stateless-applica
请阅读[运行无状态的 Replication Controller](/docs/tutorials/stateless-application/run-stateless-ap-replication-controller/)。
{{% /capture %}}
content/zh/docs/concepts/workloads/controllers/statefulset.md
+9 -8
View File
@@ -1,6 +1,6 @@
---
title: StatefulSets
content_template: templates/concept
content_type: concept
weight: 40
---
@@ -14,12 +14,12 @@ reviewers:
- kow3ns
- smarterclayton
title: StatefulSets
content_template: templates/concept
content_type: concept
weight: 40
---
-->
{{% capture overview %}}
<!-- overview -->
<!--
StatefulSet is the workload API object used to manage stateful applications.
@@ -28,9 +28,9 @@ StatefulSet is the workload API object used to manage stateful applications.
StatefulSet 是用来管理有状态应用的工作负载 API 对象。
{{< glossary_definition term_id="statefulset" length="all" >}}
{{% /capture %}}
{{% capture body %}}
<!-- body -->
<!--
## Using StatefulSets
@@ -433,8 +433,9 @@ StatefulSet will then begin to recreate the Pods using the reverted template.
恢复模板后，还必须删除 StatefulSet 尝试使用错误的配置来运行的 Pod。这样，StatefulSet 才会开始使用被还原的模板来重新创建 Pod。
{{% /capture %}}
{{% capture whatsnext %}}
## {{% heading "whatsnext" %}}
<!--
* Follow an example of [deploying a stateful application](/docs/tutorials/stateful-application/basic-stateful-set/).
@@ -446,5 +447,5 @@ StatefulSet will then begin to recreate the Pods using the reverted template.
* 示例二：[使用 StatefulSet 部署 Cassandra](/docs/tutorials/stateful-application/cassandra/)。
* 示例三：[运行多副本的有状态应用程序](/docs/tasks/run-application/run-replicated-stateful-application/)。
{{% /capture %}}
content/zh/docs/concepts/workloads/controllers/ttlafterfinished.md
+9 -8
View File
@@ -1,6 +1,6 @@
---
title: 已完成资源的 TTL 控制器
content_template: templates/concept
content_type: concept
weight: 65
---
<!--
@@ -8,12 +8,12 @@ weight: 65
reviewers:
- janetkuo
title: TTL Controller for Finished Resources
content_template: templates/concept
content_type: concept
weight: 65
---
-->
{{% capture overview %}}
<!-- overview -->
{{< feature-state for_k8s_version="v1.12" state="alpha" >}}
@@ -33,10 +33,10 @@ Alpha Disclaimer: this feature is currently alpha, and can be enabled with both
-->
Alpha 免责声明：此功能目前是 alpha 版，并且可以通过 kube-apiserver 和 kube-controller-manager [特性开关](/docs/reference/command-line-tools-reference/feature-gates/) `TTLAfterFinished` 启用。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
<!--
## TTL Controller
@@ -124,9 +124,10 @@ very small. Please be aware of this risk when setting a non-zero TTL.
-->
在 Kubernetes 中，需要在所有节点上运行 NTP（参见 [#6159](https://github.com/kubernetes/kubernetes/issues/6159#issuecomment-93844058)）以避免时间偏差。时钟并不总是如此正确，但差异应该很小。设置非零 TTL 时请注意避免这种风险。
{{% /capture %}}
{{% capture whatsnext %}}
## {{% heading "whatsnext" %}}
<!--
[Clean up Jobs automatically](/docs/concepts/workloads/controllers/jobs-run-to-completion/#clean-up-finished-jobs-automatically)
@@ -138,4 +139,4 @@ very small. Please be aware of this risk when setting a non-zero TTL.
-->
[设计文档](https://github.com/kubernetes/enhancements/blob/master/keps/sig-apps/0026-ttl-after-finish.md)
{{% /capture %}}