From 4e1e5fd2d309c3b0af3a0fa9809b9510912a351c Mon Sep 17 00:00:00 2001 From: Sunny Date: Thu, 20 Sep 2018 16:53:16 +0530 Subject: [PATCH] PV: Add StorageOS in the mount options supported list (#10334) * PV: Add StorageOS in the mount options supported list StorageOS in-tree storage plugin uses the mount options specified in the volume spec https://github.com/kubernetes/kubernetes/blob/v1.13.0-alpha.0/pkg/volume/storageos/storageos.go#L139 * Mount options volume list sort alphabetically --- .../docs/concepts/storage/persistent-volumes.md | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/content/en/docs/concepts/storage/persistent-volumes.md b/content/en/docs/concepts/storage/persistent-volumes.md index c81e098190..8d89dce258 100644 --- a/content/en/docs/concepts/storage/persistent-volumes.md +++ b/content/en/docs/concepts/storage/persistent-volumes.md @@ -383,18 +383,19 @@ A Kubernetes administrator can specify additional mount options for when a Persi The following volume types support mount options: -* GCEPersistentDisk * AWSElasticBlockStore -* AzureFile * AzureDisk -* NFS -* iSCSI -* RBD (Ceph Block Device) +* AzureFile * CephFS * Cinder (OpenStack block storage) +* GCEPersistentDisk * Glusterfs -* VsphereVolume +* NFS * Quobyte Volumes +* RBD (Ceph Block Device) +* StorageOS +* VsphereVolume +* iSCSI Mount options are not validated, so mount will simply fail if one is invalid. @@ -657,4 +658,4 @@ and need persistent storage, we recommend that you use the following pattern: or the cluster has no storage system (in which case the user cannot deploy config requiring PVCs). -{{% /capture %}} \ No newline at end of file +{{% /capture %}}