Enable storage class support in Azure File volume

Signed-off-by: Huamin Chen <hchen@redhat.com>
This commit is contained in:
Huamin Chen
2017-02-22 13:58:34 -05:00
parent 7a06e41f93
commit 6782a48dfa
11 changed files with 377 additions and 5 deletions

View File

@@ -242,7 +242,7 @@ Create a Pod to use the PVC:
$ kubectl create -f examples/persistent-volume-provisioning/quobyte/example-pod.yaml
```
#### Azure Disk
#### <a name="azure-disk">Azure Disk</a>
```yaml
kind: StorageClass
@@ -260,6 +260,22 @@ parameters:
* `location`: Azure storage account location. Default is empty.
* `storageAccount`: Azure storage account name. If storage account is not provided, all storage accounts associated with the resource group are searched to find one that matches `skuName` and `location`. If storage account is provided, it must reside in the same resource group as the cluster, and `skuName` and `location` are ignored.
#### Azure File
```yaml
kind: StorageClass
apiVersion: storage.k8s.io/v1beta1
metadata:
name: slow
provisioner: kubernetes.io/azure-file
parameters:
skuName: Standard_LRS
location: eastus
storageAccount: azure_storage_account_name
```
The parameters are the same as those used by [Azure Disk](#azure-disk)
### User provisioning requests
Users request dynamically provisioned storage by including a storage class in their `PersistentVolumeClaim`.