Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Adding content for allowVolumeExpansion field in StorageClass #15604

Merged
merged 1 commit into from Sep 3, 2019
Merged

Adding content for allowVolumeExpansion field in StorageClass #15604

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
26 changes: 26 additions & 0 deletions content/en/docs/concepts/storage/storage-classes.md
View file
Open in desktop
Expand Up @@ -53,6 +53,7 @@ provisioner: kubernetes.io/aws-ebs
parameters:
type: gp2
reclaimPolicy: Retain
allowVolumeExpansion: true
mountOptions:
- debug
volumeBindingMode: Immediate
Expand Down Expand Up @@ -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

savitharaghunathan marked this conversation as resolved.
Show resolved Hide resolved
{{< 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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@gnufied, can you verify which version all of these plugins were implemented in?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ping @gnufied for confirmation :)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

here is support/version matrix of various volume types look like:

  • EBS (1.11)
  • Cinder (1.11)
  • Glusterfs (1.11)
  • GCE PD (1.11)
  • Portworx (1.11)
  • Azure File (1.11)
  • RBD (1.11)
  • Azure Disk(1.11)
  • Flex Volume (1.13)
  • CSI (1.14, 1.15 - Alpha, 1.16 beta)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It might be worth updating this document and explicitly specify which version of k8s the volume plugin type supported expansion.

* 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
Expand Down