Skip to content

Commit c37cac5

Browse files
authored
Merge pull request #25188 from tengqm/zh-sync-12
[zh] Sync changes from English site (12)
2 parents a7a9a04 + 81bc520 commit c37cac5

15 files changed

+472
-347
lines changed

content/zh/docs/concepts/workloads/pods/_index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -281,8 +281,8 @@ PodTemplates are specifications for creating Pods, and are included in workload
281281
-->
282282
### Pod 模版 {#pod-templates}
283283

284-
{{< glossary_tooltip text="负载" term_id="workload" >}}资源的控制器通常使用 _Pod 模板(Pod Template)_
285-
来替你创建 Pod 并管理它们。
284+
{{< glossary_tooltip text="负载" term_id="workload" >}}资源的控制器通常使用
285+
_Pod 模板(Pod Template)_ 来替你创建 Pod 并管理它们。
286286

287287
Pod 模板是包含在工作负载对象中的规范,用来创建 Pod。这类负载资源包括
288288
[Deployment](/zh/docs/concepts/workloads/controllers/deployment/)

content/zh/docs/tasks/configure-pod-container/configure-persistent-volume-storage.md

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -18,14 +18,14 @@ This page shows how to configure a Pod to use a
1818
for storage.
1919
Here is a summary of the process:
2020
21-
1. A cluster administrator creates a PersistentVolume that is backed by physical
22-
storage. The administrator does not associate the volume with any Pod.
21+
1. You, as cluster administrator, create a PersistentVolume backed by physical
22+
storage. You do not associate the volume with any Pod.
2323
2424
1. You, now taking the role of a developer / cluster user, create a
2525
PersistentVolumeClaim that is automatically bound to a suitable
2626
PersistentVolume.
2727
28-
1. The user creates a Pod that uses the PersistentVolumeClaim as storage.
28+
1. You create a Pod that uses the above PersistentVolumeClaim for storage.
2929
-->
3030
本文介绍如何配置 Pod 使用
3131
{{< glossary_tooltip text="PersistentVolumeClaim" term_id="persistent-volume-claim" >}}
@@ -45,15 +45,16 @@ PersistentVolume.
4545
* You need to have a Kubernetes cluster that has only one Node, and the kubectl
4646
command-line tool must be configured to communicate with your cluster. If you
4747
do not already have a single-node cluster, you can create one by using
48-
[Minikube](/docs/getting-started-guides/minikube).
48+
[Minikube](https://minikube.sigs.k8s.io/docs/).
4949
5050
* Familiarize yourself with the material in
5151
[Persistent Volumes](/docs/concepts/storage/persistent-volumes/).
5252
-->
5353

5454
* 你需要一个包含单个节点的 Kubernetes 集群,并且必须配置 kubectl 命令行工具以便与集群交互。
55-
如果还没有单节点集群,可以使用 [Minikube](/zh/docs/setup/learning-environment/minikube/) 创建一个。
56-
55+
如果还没有单节点集群,可以使用
56+
[Minikube](https://minikube.sigs.k8s.io/docs/) 创建一个。
57+
.
5758
* 熟悉[持久卷](/zh/docs/concepts/storage/persistent-volumes/)中的材料。
5859

5960
<!-- steps -->
@@ -420,8 +421,8 @@ metadata:
420421
<!--
421422
When a Pod consumes a PersistentVolume that has a GID annotation, the annotated GID
422423
is applied to all Containers in the Pod in the same way that GIDs specified in the
423-
Pods security context are. Every GID, whether it originates from a PersistentVolume
424-
annotation or the Pods specification, is applied to the first process run in
424+
Pod's security context are. Every GID, whether it originates from a PersistentVolume
425+
annotation or the Pod's specification, is applied to the first process run in
425426
each Container.
426427
-->
427428
当 Pod 使用带有 GID 注解的 PersistentVolume 时,注解的 GID 会被应用于 Pod 中的所有容器,

0 commit comments

Comments
 (0)