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/tasks/run-application/configure-pdb.md
+11 -10
View File
@@ -1,16 +1,16 @@
---
title: 指定应用程序的中断预算（Disruption Budget）
content_template: templates/task
content_type: task
weight: 110
---
<!-- ---
title: Specifying a Disruption Budget for your Application
content_template: templates/task
content_type: task
weight: 110
--- -->
{{% capture overview %}}
<!-- overview -->
<!-- This page shows how to limit the number of concurrent disruptions
that your application experiences, allowing for higher availability
@@ -19,9 +19,10 @@ nodes. -->
本文展示了如何限制应用程序的并发中断数量，在允许集群管理员管理集群节点的同时保证高可用。
{{% /capture %}}
{{% capture prerequisites %}}
## {{% heading "prerequisites" %}}
<!-- * You are the owner of an application running on a Kubernetes cluster that requires
high availability. -->
@@ -39,9 +40,9 @@ nodes. -->
Pod Disruption Budgets. -->
* 用户应当与集群所有者或服务提供者确认其遵从 Pod 中断预算（Pod Disruption Budgets）的规则。
{{% /capture %}}
{{% capture steps %}}
<!-- steps -->
<!-- ## Protecting an Application with a PodDisruptionBudget -->
## 用 PodDisruptionBudget 来保护应用
@@ -56,9 +57,9 @@ nodes. -->
1. 以 YAML 文件形式定义 PDB 。
1. 通过 YAML 文件创建 PDB 对象。
{{% /capture %}}
{{% capture discussion %}}
<!-- discussion -->
<!-- ## Identify an Application to Protect -->
## 确定要保护的应用
@@ -329,6 +330,6 @@ to create PDBs whose selectors overlap. -->
用户可以令选择器选择一个内置控制器所控制 pod 的子集或父集。然而，当名字空间下存在多个 PDB 时，
用户必须小心，保证 PDB 的选择器之间不重叠。
{{% /capture %}}
content/zh/docs/tasks/run-application/delete-stateful-set.md
+11 -9
View File
@@ -6,29 +6,30 @@ reviewers:
- janetkuo
- smarterclayton
title: 删除 StatefulSet
content_template: templates/task
content_type: task
weight: 60
---
{{% capture overview %}}
<!-- overview -->
<!--
This task shows you how to delete a StatefulSet.
--->
本文介绍如何删除 StatefulSet。
{{% /capture %}}
{{% capture prerequisites %}}
## {{% heading "prerequisites" %}}
<!--
* This task assumes you have an application running on your cluster represented by a StatefulSet.
--->
* 本文假设在您的集群上已经运行了由 StatefulSet 创建的应用。
{{% /capture %}}
{{% capture steps %}}
<!-- steps -->
## 删除 StatefulSet
@@ -119,15 +120,16 @@ If you find that some pods in your StatefulSet are stuck in the 'Terminating' or
--->
如果您发现 StatefulSet 中的某些 pods 长时间处于 'Terminating' 或者 'Unknown' 状态，则可能需要手动干预以强制从 apiserver 中删除 pods。这是一项潜在的危险任务。详细信息请阅读[删除 StatefulSet 类型的 Pods](/docs/tasks/manage-stateful-set/delete-pods/)。
{{% /capture %}}
{{% capture whatsnext %}}
## {{% heading "whatsnext" %}}
<!--
Learn more about [force deleting StatefulSet Pods](/docs/tasks/run-application/force-delete-stateful-set-pod/).
--->
了解更多有关[强制删除 StatefulSet 类型的 Pods](/docs/tasks/run-application/force-delete-stateful-set-pod/)。
{{% /capture %}}
content/zh/docs/tasks/run-application/force-delete-stateful-set-pod.md
+12 -10
View File
@@ -5,7 +5,7 @@ reviewers:
- foxish
- smarterclayton
title: 强制删除 StatefulSet 类型的 Pods
content_template: templates/task
content_type: task
weight: 70
---
@@ -17,19 +17,20 @@ reviewers:
- foxish
- smarterclayton
title: Force Delete StatefulSet Pods
content_template: templates/task
content_type: task
weight: 70
---
--->
{{% capture overview %}}
<!-- overview -->
<!--
This page shows how to delete Pods which are part of a stateful set, and explains the considerations to keep in mind when doing so.
--->
本文介绍了如何删除 StatefulSet 管理的部分 pods，并且解释了这样操作时需要记住的注意事项。
{{% /capture %}}
{{% capture prerequisites %}}
## {{% heading "prerequisites" %}}
<!--
* This is a fairly advanced task and has the potential to violate some of the properties inherent to StatefulSet.
@@ -38,9 +39,9 @@ This page shows how to delete Pods which are part of a stateful set, and explain
* 这是一项相当高级的任务，并且可能会违反 StatefulSet 固有的某些属性。
* 继续任务之前，请熟悉下面列举的注意事项。
{{% /capture %}}
{{% capture steps %}}
<!-- steps -->
<!--
## StatefulSet considerations
@@ -146,13 +147,14 @@ Always perform force deletion of StatefulSet Pods carefully and with complete kn
--->
请始终谨慎地执行强制删除 StatefulSet 类型的 pods，并完全了解所涉及地风险。
{{% /capture %}}
{{% capture whatsnext %}}
## {{% heading "whatsnext" %}}
<!--
Learn more about [debugging a StatefulSet](/docs/tasks/debug-application-cluster/debug-stateful-set/).
--->
进一步了解[调试 StatefulSet](/docs/tasks/debug-application-cluster/debug-stateful-set/)。
{{% /capture %}}
content/zh/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md
+10 -9
View File
@@ -5,11 +5,11 @@ reviewers:
- justinsb
- directxman12
title: Horizontal Pod Autoscaler演练
content_template: templates/task
content_type: task
weight: 100
---
{{% capture overview %}}
<!-- overview -->
<!--
Horizontal Pod Autoscaler automatically scales the number of pods
@@ -25,11 +25,12 @@ This document walks you through an example of enabling Horizontal Pod Autoscaler
本文将引导您了解如何为 php-apache 服务器配置和使用 Horizontal Pod Autoscaler。
更多 Horizontal Pod Autoscaler 的信息请参阅 [Horizontal Pod Autoscaler user guide](/docs/tasks/run-application/horizontal-pod-autoscale/)。
{{% /capture %}}
{{% capture prerequisites %}}
## {{% heading "prerequisites" %}}
<!--
This example requires a running Kubernetes cluster and kubectl, version 1.2 or later.
@@ -55,9 +56,9 @@ See the [Horizontal Pod Autoscaler user guide](/docs/tasks/run-application/horiz
最后，如果要使用与 Kubernetes 对象无关的度量指标，则 Kubernetes 集群版本至少需要达到1.10版本，同样，需要保证集群能够与提供这些外部指标的API服务器通信。
更多详细信息，请参阅[Horizontal Pod Autoscaler user guide](/docs/tasks/run-application/horizontal-pod-autoscale/#support-for-custom-metrics)。
{{% /capture %}}
{{% capture steps %}}
<!-- steps -->
<!--
## Run & expose php-apache server
@@ -261,9 +262,9 @@ Autoscaling the replicas may take a few minutes.
自动伸缩完成副本数量的改变可能需要几分钟的时间。
{{< /note >}}
{{% /capture %}}
{{% capture discussion %}}
<!-- discussion -->
<!--
## Autoscaling on multiple metrics and custom metrics
@@ -690,4 +691,4 @@ kubectl create -f https://k8s.io/examples/application/hpa/php-apache.yaml
horizontalpodautoscaler.autoscaling/php-apache created
```
{{% /capture %}}
content/zh/docs/tasks/run-application/horizontal-pod-autoscale.md
+8 -7
View File
@@ -9,11 +9,11 @@ feature:
description: >
使用一个简单的命令、一个UI或基于CPU使用情况自动对应用程序进行伸缩。
content_template: templates/concept
content_type: concept
weight: 90
---
{{% capture overview %}}
<!-- overview -->
<!--
The Horizontal Pod Autoscaler automatically scales the number of pods
@@ -36,10 +36,10 @@ to match the observed average CPU utilization to the target specified by user.
Pod 水平自动伸缩特性由 Kubernetes API 资源和控制器实现。资源决定了控制器的行为。
控制器会周期性的获取平均 CPU 利用率，并与目标值相比较后来调整 replication controller 或 deployment 中的副本数量。
{{% /capture %}}
{{% capture body %}}
<!-- body -->
<!--
## How does the Horizontal Pod Autoscaler work?
@@ -543,9 +543,10 @@ and [the walkthrough for using external metrics](/docs/tasks/run-application/hor
[the walkthrough for using custom metrics](/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough/#autoscaling-on-multiple-metrics-and-custom-metrics)
和 [the walkthrough for using external metrics](/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough/#autoscaling-on-metrics-not-related-to-kubernetes-objects)。
{{% /capture %}}
{{% capture whatsnext %}}
## {{% heading "whatsnext" %}}
<!--
* Design documentation: [Horizontal Pod Autoscaling](https://git.k8s.io/community/contributors/design-proposals/autoscaling/horizontal-pod-autoscaler.md).
@@ -556,4 +557,4 @@ and [the walkthrough for using external metrics](/docs/tasks/run-application/hor
* kubectl 自动缩放命令： [kubectl autoscale](/docs/reference/generated/kubectl/kubectl-commands/#autoscale).
* 使用示例：[Horizontal Pod Autoscaler](/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough/).
{{% /capture %}}
content/zh/docs/tasks/run-application/rolling-update-replication-controller.md
+2 -2
View File
@@ -2,7 +2,7 @@
reviewers:
- janetkuo
title: 基于Replication Controller执行滚动升级
content_template: templates/concept
content_type: concept
weight: 80
---
@@ -11,7 +11,7 @@ weight: 80
reviewers:
- janetkuo
title: Perform Rolling Update Using a Replication Controller
content_template: templates/concept
content_type: concept
weight: 80
---
-->
content/zh/docs/tasks/run-application/run-replicated-stateful-application.md
+18 -14
View File
@@ -1,6 +1,6 @@
---
title: 运行一个有状态的应用程序
content_template: templates/tutorial
content_type: tutorial
weight: 30
---
<!-- ---
@@ -12,11 +12,11 @@ reviewers:
- kow3ns
- smarterclayton
title: Run a Replicated Stateful Application
content_template: templates/tutorial
content_type: tutorial
weight: 30
--- -->
{{% capture overview %}}
<!-- overview -->
<!-- This page shows how to run a replicated stateful application using a
[StatefulSet](/docs/concepts/workloads/controllers/statefulset/) controller.
@@ -30,9 +30,10 @@ on general patterns for running stateful applications in Kubernetes. -->
请注意 **这不是生产配置**。
重点是， MySQL 设置保留在不安全的默认值上，使重点放在 Kubernetes 中运行有状态应用程序的常规模式。
{{% /capture %}}
{{% capture prerequisites %}}
## {{% heading "prerequisites" %}}
<!-- * {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
* {{< include "default-storage-class-prereqs.md" >}}
@@ -54,9 +55,10 @@ on general patterns for running stateful applications in Kubernetes. -->
[ConfigMaps](/docs/tasks/configure-pod-container/configure-pod-configmap/).
* 熟悉 MySQL 会有所帮助，但是本教程旨在介绍对其他系统应该有用的常规模式。
{{% /capture %}}
{{% capture objectives %}}
## {{% heading "objectives" %}}
<!-- * Deploy a replicated MySQL topology with a StatefulSet controller.
* Send MySQL client traffic.
@@ -67,9 +69,9 @@ on general patterns for running stateful applications in Kubernetes. -->
* 观察对宕机的抵抗力。
* 缩放 StatefulSet 的大小。
{{% /capture %}}
{{% capture lessoncontent %}}
<!-- lessoncontent -->
<!-- ## Deploy MySQL -->
## 部署 MySQL
@@ -590,9 +592,10 @@ kubectl delete pvc data-mysql-3
kubectl delete pvc data-mysql-4
```
{{% /capture %}}
{{% capture cleanup %}}
## {{% heading "cleanup" %}}
<!-- 1. Cancel the `SELECT @@server_id` loop by pressing **Ctrl+C** in its terminal,
or running the following from another terminal: -->
@@ -642,15 +645,16 @@ kubectl delete pvc data-mysql-4
如果您使用了动态预配器，当得知您删除 PersistentVolumeClaims 时，它将自动删除 PersistentVolumes。
一些动态预配器(例如用于 EBS 和 PD 的预配器)也会在删除 PersistentVolumes 时释放基础资源。
{{% /capture %}}
{{% capture whatsnext %}}
## {{% heading "whatsnext" %}}
<!-- * Look in the [Helm Charts repository](https://github.com/kubernetes/charts)
for other stateful application examples. -->
* 在[Helm Charts 存储库](https://github.com/kubernetes/charts)中查找其他有状态的应用程序示例。
{{% /capture %}}
content/zh/docs/tasks/run-application/run-single-instance-stateful-application.md
+14 -11
View File
@@ -1,33 +1,35 @@
---
title: 运行一个单实例有状态应用
content_template: templates/tutorial
content_type: tutorial
---
{{% capture overview %}}
<!-- overview -->
本文介绍在 Kubernetes 中使用 PersistentVolume 和 Deployment 如何运行一个单实例有状态应用. 该应用是 MySQL.
{{% /capture %}}
{{% capture objectives %}}
## {{% heading "objectives" %}}
* 在环境中通过磁盘创建一个PersistentVolume.
* 创建一个MySQL Deployment.
* 在集群内以一个已知的 DNS 名将 MySQL 暴露给其他 pods.
{{% /capture %}}
{{% capture prerequisites %}}
## {{% heading "prerequisites" %}}
* {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
* {{< include "default-storage-class-prereqs.md" >}}
{{% /capture %}}
{{% capture lessoncontent %}}
<!-- lessoncontent -->
## 部署MySQL
@@ -158,10 +160,11 @@ kubectl delete pv mysql-pv-volume
如果通过手动的方式分配 PersistentVolume, 那么也需要手动的删除它，以及释放下层资源.
如果是用过动态分配 PersistentVolume 的方式，在删除 PersistentVolumeClaim 后 PersistentVolume 将被自动的删除. 一些存储服务(比如 EBS 和 PD)也会在 PersistentVolume 被删除时自动回收下层资源.
{{% /capture %}}
{{% capture whatsnext %}}
## {{% heading "whatsnext" %}}
* 了解更多 Deployment 对象请参考 [Deployment objects](/docs/concepts/workloads/controllers/deployment/).
@@ -171,6 +174,6 @@ kubectl delete pv mysql-pv-volume
* 卷和持久卷请参考 [Volumes](/docs/concepts/storage/volumes/) 和 [Persistent Volumes](/docs/concepts/storage/persistent-volumes/)
{{% /capture %}}
content/zh/docs/tasks/run-application/run-stateless-application-deployment.md
+14 -11
View File
@@ -1,32 +1,34 @@
---
title: 使用Deployment运行一个无状态应用
content_template: templates/tutorial
content_type: tutorial
---
{{% capture overview %}}
<!-- overview -->
本文介绍通过Kubernetes Deployment对象如何去运行一个应用.
{{% /capture %}}
{{% capture objectives %}}
## {{% heading "objectives" %}}
* 创建一个nginx deployment.
* 使用kubectl列举关于deployment信息.
* 更新deployment.
{{% /capture %}}
{{% capture prerequisites %}}
## {{% heading "prerequisites" %}}
{{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
{{% /capture %}}
{{% capture lessoncontent %}}
<!-- lessoncontent -->
## 创建和探究一个nginx deployment
@@ -132,13 +134,14 @@ content_template: templates/tutorial
创建一个多副本应用首选方法是使用Deployment,反过来使用ReplicaSet. 在Deployment和ReplicaSet加入到Kubernetes之前, 多副本应用通过[ReplicationController](/docs/concepts/workloads/controllers/replicationcontroller/)来配置.
{{% /capture %}}
{{% capture whatsnext %}}
## {{% heading "whatsnext" %}}
* 了解更多 [Deployment objects](/docs/concepts/workloads/controllers/deployment/).
{{% /capture %}}
content/zh/docs/tasks/run-application/scale-stateful-set.md
+11 -9
View File
@@ -8,22 +8,23 @@ approvers:
- kow3ns
- smarterclayton
title: 弹缩StatefulSet
content_template: templates/task
content_type: task
---
{{% capture overview %}}
<!-- overview -->
本文介绍如何弹缩StatefulSet.
{{% /capture %}}
{{% capture prerequisites %}}
## {{% heading "prerequisites" %}}
* StatefulSets仅适用于Kubernetes1.5及以上版本.
* **不是所有Stateful应用都适合弹缩.** 在弹缩前您的应用前. 您必须充分了解您的应用, 不适当的弹缩StatefulSet或许会造成应用自身功能的不稳定.
* 仅当您确定该Stateful应用的集群是完全健康才可执行弹缩操作.
{{% /capture %}}
{{% capture steps %}}
<!-- steps -->
## 使用 `kubectl` 弹缩StatefulSets
@@ -79,12 +80,13 @@ StatefulSet的扩容/缩容操作. 一些分布式数据库在节点加入和同
这些情况下，最好是在应用级别进行弹缩操作, 并且只有在您确保Stateful应用的集群是完全健康时才执行弹缩.
{{% /capture %}}
{{% capture whatsnext %}}
## {{% heading "whatsnext" %}}
了解更多 [deleting a StatefulSet](/docs/tasks/manage-stateful-set/deleting-a-statefulset/).
{{% /capture %}}
content/zh/docs/tasks/run-application/update-api-object-kubectl-patch.md
+12 -10
View File
@@ -1,7 +1,7 @@
---
title: 使用 kubectl patch 更新 API 对象
description: 使用 kubectl patch 更新 Kubernetes API 对象。做一个策略性的合并 patch 或 JSON 合并 patch。
content_template: templates/task
content_type: task
weight: 40
---
@@ -9,12 +9,12 @@ weight: 40
---
title: Update API Objects in Place Using kubectl patch
description: Use kubectl patch to update Kubernetes API objects in place. Do a strategic merge patch or a JSON merge patch.
content_template: templates/task
content_type: task
weight: 40
---
-->
{{% capture overview %}}
<!-- overview -->
<!--
This task shows how to use `kubectl patch` to update an API object in place. The exercises
@@ -23,16 +23,17 @@ in this task demonstrate a strategic merge patch and a JSON merge patch.
这个任务展示了如何使用 `kubectl patch` 就地更新 API 对象。这个任务中的练习演示了一个策略性合并 patch 和一个 JSON 合并 patch。
{{% /capture %}}
{{% capture prerequisites %}}
## {{% heading "prerequisites" %}}
{{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
{{% /capture %}}
{{% capture steps %}}
<!-- steps -->
<!--
## Use a strategic merge patch to update a Deployment
@@ -505,10 +506,11 @@ and
和
[kubectl apply](/docs/reference/generated/kubectl/kubectl-commands/#apply)。
{{% /capture %}}
{{% capture whatsnext %}}
## {{% heading "whatsnext" %}}
<!--
* [Kubernetes Object Management](/docs/concepts/overview/object-management-kubectl/overview/)
@@ -522,6 +524,6 @@ and
* [使用配置文件强制管理 Kubernetes 对象](/docs/concepts/overview/object-management-kubectl/imperative-config/)
* [使用配置文件对 Kubernetes 对象进行声明式管理](/docs/concepts/overview/object-management-kubectl/declarative-config/)
{{% /capture %}}