@@ -103,22 +103,22 @@ for provisioning PVs. This field must be specified.
103
103
| Volume Plugin | Internal Provisioner | Config Example |
104
104
-->
105
105
106
- | 卷插件 | 内置制备器 | 配置示例 |
107
- | :------------------- | :------------------ : | :-----------------------------------: |
108
- | AWSElasticBlockStore | ✓ | [AWS EBS](#aws-ebs) |
109
- | AzureFile | ✓ | [Azure File](#azure-file) |
110
- | AzureDisk | ✓ | [Azure Disk](#azure-disk) |
111
- | CephFS | - | - |
112
- | Cinder | ✓ | [OpenStack Cinder](#openstack-cinder) |
113
- | FC | - | - |
114
- | FlexVolume | - | - |
115
- | GCEPersistentDisk | ✓ | [GCE PD](#gce-pd) |
116
- | iSCSI | - | - |
117
- | NFS | - | [NFS](#nfs) |
118
- | RBD | ✓ | [Ceph RBD](#ceph-rbd) |
119
- | VsphereVolume | ✓ | [vSphere](#vsphere) |
120
- | PortworxVolume | ✓ | [Portworx Volume](#portworx-volume) |
121
- | Local | - | [Local](#local) |
106
+ | 卷插件 | 内置制备器 | 配置示例 |
107
+ | :------------------- | :--------: | :-----------------------------------: |
108
+ | AWSElasticBlockStore | ✓ | [AWS EBS](#aws-ebs) |
109
+ | AzureFile | ✓ | [Azure File](#azure-file) |
110
+ | AzureDisk | ✓ | [Azure Disk](#azure-disk) |
111
+ | CephFS | - | - |
112
+ | Cinder | ✓ | [OpenStack Cinder](#openstack-cinder) |
113
+ | FC | - | - |
114
+ | FlexVolume | - | - |
115
+ | GCEPersistentDisk | ✓ | [GCE PD](#gce-pd) |
116
+ | iSCSI | - | - |
117
+ | NFS | - | [NFS](#nfs) |
118
+ | RBD | ✓ | [Ceph RBD](#ceph-rbd) |
119
+ | VsphereVolume | ✓ | [vSphere](#vsphere) |
120
+ | PortworxVolume | ✓ | [Portworx Volume](#portworx-volume) |
121
+ | Local | - | [Local](#local) |
122
122
123
123
<!--
124
124
You are not restricted to specifying the "internal" provisioners
@@ -155,7 +155,8 @@ vendors provide their own external provisioner.
155
155
### Reclaim Policy
156
156
157
157
PersistentVolumes that are dynamically created by a StorageClass will have the
158
- reclaim policy specified in the ` reclaimPolicy` field of the class, which can be
158
+ [reclaim policy](/docs/concepts/storage/persistent-volumes/#reclaiming)
159
+ specified in the ` reclaimPolicy` field of the class, which can be
159
160
either `Delete` or `Retain`. If no `reclaimPolicy` is specified when a
160
161
StorageClass object is created, it will default to `Delete`.
161
162
@@ -164,8 +165,10 @@ whatever reclaim policy they were assigned at creation.
164
165
-->
165
166
# ## 回收策略 {#reclaim-policy}
166
167
167
- 由 StorageClass 动态创建的 PersistentVolume 会在类的 `reclaimPolicy` 字段中指定回收策略,可以是
168
- ` Delete` 或者 `Retain`。如果 StorageClass 对象被创建时没有指定 `reclaimPolicy`,它将默认为 `Delete`。
168
+ 由 StorageClass 动态创建的 PersistentVolume 会在类的
169
+ [reclaimPolicy](/zh-cn/docs/concepts/storage/persistent-volumes/#reclaiming)
170
+ 字段中指定回收策略,可以是 `Delete` 或者 `Retain`。
171
+ 如果 StorageClass 对象被创建时没有指定 `reclaimPolicy`,它将默认为 `Delete`。
169
172
170
173
通过 StorageClass 手动创建并管理的 PersistentVolume 会使用它们被创建时指定的回收策略。
171
174
@@ -236,8 +239,9 @@ the class or PV. If a mount option is invalid, the PV mount fails.
236
239
# ## 卷绑定模式 {#volume-binding-mode}
237
240
238
241
<!--
239
- The `volumeBindingMode` field controls when [volume binding and dynamic
240
- provisioning](/docs/concepts/storage/persistent-volumes/#provisioning) should occur. When unset, "Immediate" mode is used by default.
242
+ The `volumeBindingMode` field controls when
243
+ [volume binding and dynamic provisioning](/docs/concepts/storage/persistent-volumes/#provisioning)
244
+ should occur. When unset, "Immediate" mode is used by default.
241
245
-->
242
246
` volumeBindingMode`
243
247
字段控制了[卷绑定和动态制备](/zh-cn/docs/concepts/storage/persistent-volumes/#provisioning)应该发生在什么时候。
@@ -310,7 +314,8 @@ to see its supported topology keys and examples.
310
314
{{< note >}}
311
315
<!--
312
316
If you choose to use `WaitForFirstConsumer`, do not use `nodeName` in the Pod spec
313
- to specify node affinity. If `nodeName` is used in this case, the scheduler will be bypassed and PVC will remain in `pending` state.
317
+ to specify node affinity.
318
+ If `nodeName` is used in this case, the scheduler will be bypassed and PVC will remain in `pending` state.
314
319
315
320
Instead, you can use node selector for hostname in this case as shown below.
316
321
-->
@@ -493,6 +498,7 @@ parameters:
493
498
where Kubernetes cluster has a node. `zone` and `zones` parameters must not
494
499
be used at the same time.
495
500
- `fstype` : ` ext4` or `xfs`. Default: `ext4`. The defined filesystem type must be supported by the host operating system.
501
+
496
502
- `replication-type` : ` none` or `regional-pd`. Default: `none`.
497
503
-->
498
504
- ` type` :`pd-standard` 或者 `pd-ssd`。默认:`pd-standard`
@@ -561,11 +567,12 @@ parameters:
561
567
- ` readOnly` :是否将存储挂载为只读的标志(默认为 false)。
562
568
563
569
<!--
564
- Kubernetes doesn't include an internal NFS provisioner. You need to use an external provisioner to create a StorageClass for NFS.
570
+ Kubernetes doesn't include an internal NFS provisioner.
571
+ You need to use an external provisioner to create a StorageClass for NFS.
565
572
Here are some examples :
566
573
567
- * [NFS Ganesha server and external provisioner](https://github.com/kubernetes-sigs/nfs-ganesha-server-and-external-provisioner)
568
- * [NFS subdir external provisioner](https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner)
574
+ - [NFS Ganesha server and external provisioner](https://github.com/kubernetes-sigs/nfs-ganesha-server-and-external-provisioner)
575
+ - [NFS subdir external provisioner](https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner)
569
576
-->
570
577
Kubernetes 不包含内部 NFS 驱动。你需要使用外部驱动为 NFS 创建 StorageClass。
571
578
这里有些例子:
@@ -591,10 +598,11 @@ parameters:
591
598
- ` availability` :可用区域。如果没有指定,通常卷会在 Kubernetes 集群节点所在的活动区域中轮转调度。
592
599
593
600
{{< note >}}
601
+ {{< feature-state state="deprecated" for_k8s_version="v1.11" >}}
594
602
<!--
595
- This internal provisioner of OpenStack is deprecated. Please use [the external cloud provider for OpenStack](https://github.com/kubernetes/cloud-provider-openstack).
603
+ This internal provisioner of OpenStack is deprecated. Please use
604
+ [the external cloud provider for OpenStack](https://github.com/kubernetes/cloud-provider-openstack).
596
605
-->
597
- {{< feature-state state="deprecated" for_k8s_version="v1.11" >}}
598
606
OpenStack 的内部驱动已经被弃用。请使用
599
607
[OpenStack 的外部云驱动](https://github.com/kubernetes/cloud-provider-openstack)。
600
608
{{< /note >}}
@@ -607,7 +615,10 @@ There are two types of provisioners for vSphere storage classes:
607
615
- [CSI provisioner](#vsphere-provisioner-csi): `csi.vsphere.vmware.com`
608
616
- [vCP provisioner](#vcp-provisioner): `kubernetes.io/vsphere-volume`
609
617
610
- In-tree provisioners are [deprecated](/blog/2019/12/09/kubernetes-1-17-feature-csi-migration-beta/#why-are-we-migrating-in-tree-plugins-to-csi). For more information on the CSI provisioner, see [Kubernetes vSphere CSI Driver](https://vsphere-csi-driver.sigs.k8s.io/) and [vSphereVolume CSI migration](/docs/concepts/storage/volumes/#vsphere-csi-migration).
618
+ In-tree provisioners are [deprecated](/blog/2019/12/09/kubernetes-1-17-feature-csi-migration-beta/#why-are-we-migrating-in-tree-plugins-to-csi).
619
+ For more information on the CSI provisioner, see
620
+ [Kubernetes vSphere CSI Driver](https://vsphere-csi-driver.sigs.k8s.io/) and
621
+ [vSphereVolume CSI migration](/docs/concepts/storage/volumes/#vsphere-csi-migration).
611
622
-->
612
623
vSphere 存储类有两种制备器:
613
624
@@ -623,7 +634,8 @@ vSphere 存储类有两种制备器:
623
634
<!--
624
635
# ### CSI Provisioner {#vsphere-provisioner-csi}
625
636
626
- The vSphere CSI StorageClass provisioner works with Tanzu Kubernetes clusters. For an example, refer to the [vSphere CSI repository](https://github.com/kubernetes-sigs/vsphere-csi-driver/blob/master/example/vanilla-k8s-RWM-filesystem-volumes/example-sc.yaml).
637
+ The vSphere CSI StorageClass provisioner works with Tanzu Kubernetes clusters.
638
+ For an example, refer to the [vSphere CSI repository](https://github.com/kubernetes-sigs/vsphere-csi-driver/blob/master/example/vanilla-k8s-RWM-filesystem-volumes/example-sc.yaml).
627
639
-->
628
640
# ### CSI 制备器 {#vsphere-provisioner-csi}
629
641
0 commit comments