|
1 | 1 | ## `blobfuse.csi.azure.com` driver parameters
|
2 | 2 | > storage class `blobfuse.csi.azure.com` parameters are compatible with built-in [blobfuse](https://kubernetes.io/docs/concepts/storage/volumes/#blobfuse) plugin
|
| 3 | + |
| 4 | + > parameter names are case-insensitive |
3 | 5 |
|
4 | 6 | - Dynamic Provisioning
|
5 | 7 | > get a quick example [here](../deploy/example/storageclass-blobfuse-csi.yaml)
|
6 | 8 |
|
7 | 9 | Name | Meaning | Example | Mandatory | Default value
|
8 | 10 | --- | --- | --- | --- | ---
|
9 | 11 | skuName | blobfuse storage account type (alias: `storageAccountType`) | `Standard_LRS`, `Standard_GRS`, `Standard_RAGRS` | No | `Standard_LRS`
|
10 |
| -storageAccount | specify the storage account name in which blobfuse share will be created | STORAGE_ACCOUNT_NAME | Yes | if empty, driver will find a suitable storage account that matches `skuName` in the same resource group; if a storage account name is provided, it means that storage account must exist otherwise there would be error |
11 | 12 | location | specify the location in which blobfuse share will be created | `eastus`, `westus`, etc. | No | if empty, driver will use the same location name as current k8s cluster
|
12 |
| -resourceGroup | specify the existing resource group name where the container is | existing resource group name | Yes | if empty, driver will use the same resource group name as current k8s cluster |
13 |
| -containername | specify the existing container name where blob storage will be created | existing container name | No | if empty, driver will create a new container name, starting with `pvc-fuse` |
| 13 | +resourceGroup | specify the existing resource group name where the container is | existing resource group name | No | if empty, driver will use the same resource group name as current k8s cluster |
| 14 | +storageAccount | specify the storage account name in which blobfuse share will be created | STORAGE_ACCOUNT_NAME | No | if empty, driver will find a suitable storage account that matches `skuName` in the same resource group; if a storage account name is provided, it means that storage account must exist otherwise there would be error |
| 15 | +containerName | specify the existing container name where blob storage will be created | existing container name | No | if empty, driver will create a new container name, starting with `pvc-fuse` |
14 | 16 |
|
15 | 17 | - Static Provisioning(use existing storage container)
|
16 | 18 | > get a quick example [here](../deploy/example/pv-blobfuse-csi.yaml)
|
17 | 19 |
|
18 | 20 | Name | Meaning | Available Value | Mandatory | Default value
|
19 | 21 | --- | --- | --- | --- | ---
|
20 |
| -volumeAttributes.sharename | blobfuse share name | existing blobfuse share name | Yes | |
| 22 | +volumeAttributes.containerName | existing container name | existing container name | Yes | |
21 | 23 | nodePublishSecretRef.name | secret name that stores storage account name and key | existing secret name | Yes |
|
22 | 24 | nodePublishSecretRef.namespace | namespace where the secret is | k8s namespace | No | `default`
|
0 commit comments