- Although Blob CSI Driver allows ReadWriteMany access mode to be used, its functionality is limited by the underlying volume-mounting technology. If azure-storage-fuse is being used to mount a Blob storage container, multiple nodes are allowed to mount the same container, but for just read-only scenarios. It means, you can still use ReadWriteMany mode to claim a volume, but you should carefully avoid writing to one single file from multiple nodes as there will be data corruption. NFSv3, in the contrast, fully supports ReadWriteMany access mode.
- The azure-storage-fuse method only supports Linux agent nodes.
- For the Kubernetes clusters that are running on Azure Stack Hub environments, only Standard Locally-redundant (Standard_LRS) and Premium Locally-redundant (Premium_LRS) Storage Account types are supported.
- The memory consumption of azure-storage-fuse (blobfuse) may be high when large files are being processed. Thus, by default the Blob CSI Driver container has a memory restriction of 2100Mi. This known issue is described in this ticket.
- Restart csi-blobfuse-node daemonset would make current blobfuse mount unavailable. This issue is tracked by this ticket.