You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> storage class `blobfuse.csi.azure.com` parameters are compatible with built-in [blobfuse](https://kubernetes.io/docs/concepts/storage/volumes/#blobfuse) plugin
3
-
1
+
## Driver Parameters
4
2
> parameter names are case-insensitive
5
3
6
4
### Dynamic Provisioning
7
-
> get a quick example [here](../deploy/example/storageclass-blobfuse-csi.yaml)
5
+
> get a [example](../deploy/example/storageclass-blobfuse-csi.yaml)
8
6
9
-
> get a `mountOptions`example [here](../deploy/example/storageclass-blobfuse-csi-mountoptions.yaml)
7
+
> get a `mountOptions`[example](../deploy/example/storageclass-blobfuse-csi-mountoptions.yaml)
10
8
11
9
Name | Meaning | Example | Mandatory | Default value
12
10
--- | --- | --- | --- | ---
@@ -21,10 +19,10 @@ server | specify azure storage account server address | existing server address,
21
19
22
20
Blobfuse driver does not honor `fsGroup` securityContext setting, instead user could use `-o gid=1000` in `mountoptions` to set ownership, check [here](https://github.com/Azure/azure-storage-fuse#mount-options) for more mountoptions.
0 commit comments