@@ -18,14 +18,14 @@ This page shows how to configure a Pod to use a
18
18
for storage.
19
19
Here is a summary of the process:
20
20
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.
23
23
24
24
1. You, now taking the role of a developer / cluster user, create a
25
25
PersistentVolumeClaim that is automatically bound to a suitable
26
26
PersistentVolume.
27
27
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.
29
29
-->
30
30
本文介绍如何配置 Pod 使用
31
31
{{< glossary_tooltip text="PersistentVolumeClaim" term_id="persistent-volume-claim" >}}
@@ -45,15 +45,16 @@ PersistentVolume.
45
45
* You need to have a Kubernetes cluster that has only one Node, and the kubectl
46
46
command-line tool must be configured to communicate with your cluster. If you
47
47
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/ ).
49
49
50
50
* Familiarize yourself with the material in
51
51
[Persistent Volumes](/docs/concepts/storage/persistent-volumes/).
52
52
-->
53
53
54
54
* 你需要一个包含单个节点的 Kubernetes 集群,并且必须配置 kubectl 命令行工具以便与集群交互。
55
- 如果还没有单节点集群,可以使用 [ Minikube] ( /zh/docs/setup/learning-environment/minikube/ ) 创建一个。
56
-
55
+ 如果还没有单节点集群,可以使用
56
+ [ Minikube] ( https://minikube.sigs.k8s.io/docs/ ) 创建一个。
57
+ .
57
58
* 熟悉[ 持久卷] ( /zh/docs/concepts/storage/persistent-volumes/ ) 中的材料。
58
59
59
60
<!-- steps -->
@@ -420,8 +421,8 @@ metadata:
420
421
<!--
421
422
When a Pod consumes a PersistentVolume that has a GID annotation, the annotated GID
422
423
is applied to all Containers in the Pod in the same way that GIDs specified in the
423
- Pod’ s security context are. Every GID, whether it originates from a PersistentVolume
424
- annotation or the Pod’ s 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
425
426
each Container.
426
427
-->
427
428
当 Pod 使用带有 GID 注解的 PersistentVolume 时,注解的 GID 会被应用于 Pod 中的所有容器,
0 commit comments