Share via

blobfuse2 not installed by CSI driver

Luke Rosser 165 Reputation points
2025-09-10T08:18:50.92+00:00

Hello,

I'm using the blob.csi.azure.com storage class provisioner and want to use blobfuse2 so I can get the latest features like streaming. I created a storageclass specifying the fuse2 as the protocol, reference: https://github.com/kubernetes-sigs/blob-csi-driver/blob/e78e30a2ec51cbb5c9abfa6dcc6e868bd6bd96ed/docs/driver-parameters.md?plain=1#L112

This didn't work and continued to use blobfuse1. After inspecting the CSI daemonset I noticed blobfuse2 wasn't installing and ran this:

kubectl patch daemonset csi-blob-node -n kube-system -p '{"spec":{"template":{"spec":{"initContainers":[{"env":[{"name":"INSTALL_BLOBFUSE2","value":"true"},{"name":"BLOBFUSE2_VERSION","value":"2.5.0"}],"name":"install-blobfuse-proxy"}]}}}}'

The storage class then started to work with blobfuse2 arguments.

My question is, since this CSI service is managed by AKS, if I upgrade my AKS version will this change be removed? If there a better way to manage this within AKS so that I can make blobfuse2 available?

Azure Kubernetes Service
Azure Kubernetes Service

An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.


1 answer

Sort by: Most helpful
  1. Jilakara Hemalatha 14,115 Reputation points Microsoft External Staff Moderator
    2025-09-19T03:33:27.07+00:00

    Hi Luke Rosser,

    Thanks for your patience while we checked with the product group regarding your Blobfuse2 query. Please find the updates below:

    Blobfuse2 availability on AKS nodes:

    • Blobfuse2 is already included by default in AKS node images starting from Ubuntu 22.04.
    • When you set protocol: fuse2 in your StorageClass, the CSI driver will attempt to use Blobfuse2. If Blobfuse2 is not installed on the node, the mount operation will fail rather than fall back to Blobfuse v1
    • Please note that for existing PVs, changing the StorageClass parameters will not retroactively switch them to Blobfuse2. A new PV would need to be created with protocol: fuse2 for the setting to take effect.

    Since Blobfuse2 is part of the default AKS node image (from Ubuntu 22.04 onward), you should not need to patch the CSI DaemonSet for installation. After an upgrade, as long as your node pool uses a supported image, Blobfuse2 remains available.

    Reference: https://learn.microsoft.com/en-us/azure/aks/upgrade-os-version

    https://learn.microsoft.com/en-us/azure/aks/node-images

    To help us confirm your scenario more precisely, could you please share:

    1. The OS version and node image version of your AKS nodes (you mentioned AKS v1.31.10, but we’d like to verify the node details).
    2. Additionally, to clarify your expectation: are you specifically asking whether Blobfuse2 version 2.5.0 is installed by default on AKS nodes?

    This information will help us validate whether your environment should already include Blobfuse2 by default, or if additional action is needed.

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.