This driver allows Kubernetes to access Azure Storage through one of following methods:
csi plugin name: blob.csi.azure.com
| driver version | Image | 1.15+ | built-in blobfuse version |
|---|---|---|---|
| master branch | mcr.microsoft.com/k8s/csi/blob-csi:latest | yes | 1.3.6 |
| v0.11.0 | mcr.microsoft.com/k8s/csi/blob-csi:v0.11.0 | yes | 1.3.6 |
| v0.10.0 | mcr.microsoft.com/k8s/csi/blob-csi:v0.10.0 | yes | 1.3.5 |
| v0.9.0 | mcr.microsoft.com/k8s/csi/blob-csi:v0.9.0 | yes | 1.3.4 |
Since v0.7.0, driver name changed from blobfuse.csi.azure.com to blob.csi.azure.com, volume created by v0.6.0(or prior version) could not be mounted by v0.7.0 driver. If you have volumes created by v0.6.0 version, just keep the driver running in your cluster.
Please refer to blob.csi.azure.com driver parameters
- The driver depends on cloud provider config file, usually it's
/etc/kubernetes/azure.jsonon all kubernetes nodes deployed by AKS or aks-engine, here is azure.json example.
To specify a different cloud provider config file, create
azure-cred-fileconfigmap before driver installation, e.g. for OpenShift, it's/etc/kubernetes/cloud.conf(make sure config file path is in thevolumeMounts.mountPath)kubectl create configmap azure-cred-file --from-literal=path="/etc/kubernetes/cloud.conf" --from-literal=path-windows="C:\\k\\cloud.conf" -n kube-system
- This driver also supports read cloud config from kuberenetes secret.
- If cluster identity is Managed Service Identity(MSI), make sure user assigned identity has
Contributorrole on node resource group
- install via kubectl on public Azure (please use helm for other cloud environments, e.g. Azure Stack)
- install via helm charts on public Azure and Azure Stack
- Please see our support policy
- Please refer to Azure Blob Storage CSI Driver Limitations
- Please refer to development guide
- Check testgrid provider-azure-blobfuse-csi-driver dashboard.