Adding allowVolumeEXpansion feature to storage-classes.md file (#15604)

pull/16206/head
savitharaghunathan 2019-09-03 10:16:29 -04:00 committed by Kubernetes Prow Robot
parent 10d764adb5
commit dc5179c1c3
1 changed files with 26 additions and 0 deletions

View File

@ -53,6 +53,7 @@ provisioner: kubernetes.io/aws-ebs
parameters:
type: gp2
reclaimPolicy: Retain
allowVolumeExpansion: true
mountOptions:
- debug
volumeBindingMode: Immediate
@ -110,6 +111,31 @@ either `Delete` or `Retain`. If no `reclaimPolicy` is specified when a
Persistent Volumes that are created manually and managed via a storage class will have
whatever reclaim policy they were assigned at creation.
### Allow Volume Expansion
{{< feature-state for_k8s_version="v1.11" state="beta" >}}
Persistent Volumes can be configured to be expandable. This feature when set to `true`,
allows the users to resize the volume by editing the corresponding PVC object.
The following types of volumes support volume expansion, when the underlying
Storage Class has the field `allowVolumeExpansion` set to true.
* gcePersistentDisk
* awsElasticBlockStore
* Cinder
* glusterfs
* rbd
* Azure File
* Azure Disk
* Portworx
* FlexVolumes
* CSI {{< feature-state for_k8s_version="v1.14" state="alpha" >}}
{{< note >}}
This feature cannot be used to shrink volumes.
{{< /note >}}
### Mount Options
Persistent Volumes that are dynamically created by a storage class will have the