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

update regional pd description to use volume topology mechanism

Browse Source
This commit is contained in:
Cheng Xing
2020-04-16 17:22:39 -07:00
committed by bryan
parent d2d6c56636
commit e1c91f607e
1 changed files with 7 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/storage/storage-classes.md
+7 -6
View File
@@ -301,12 +301,13 @@ If `replication-type` is set to `none`, a regular (zonal) PD will be provisioned
If `replication-type` is set to `regional-pd`, a If `replication-type` is set to `regional-pd`, a
[Regional Persistent Disk](https://cloud.google.com/compute/docs/disks/#repds) [Regional Persistent Disk](https://cloud.google.com/compute/docs/disks/#repds)
will be provisioned. In this case, users must use `zones` instead of `zone` to will be provisioned. It's highly recommended to have
specify the desired replication zones. If exactly two zones are specified, the `volumeBindingMode: WaitForFirstConsumer` set, in which case when you create
Regional PD will be provisioned in those zones. If more than two zones are a Pod that consumes a PersistentVolumeClaim which uses this StorageClass, a
specified, Kubernetes will arbitrarily choose among the specified zones. If the Regional Persistent Disk is provisioned with two zones. One zone is the same
`zones` parameter is omitted, Kubernetes will arbitrarily choose among zones as the zone that the Pod is scheduled in. The other zone is randomly picked
managed by the cluster. from the zones available to the cluster. Disk zones can be further constrained
using `allowedTopologies`.
{{< note >}} {{< note >}}
`zone` and `zones` parameters are deprecated and replaced with `zone` and `zones` parameters are deprecated and replaced with