Azure Blob Fuse in AKS with Managed Identity

[@DavidHernandez-db4ij]

great video, excellent content as usual, thanks a lot @Houssem. Just one clarification, maybe I have misunderstood but the managed identity should be assign to the VMSS that is intended to run to workload e.g. pod where the mount occurs, not necessarily the system node pool VMSS

[@prasadvm007]

Hi @Houssem, How to use it in a private image? I'm getting user permission issue in a private image container. Error getting: ls: cannot access 'myfolder': Permission denied d????????? ? ? ? ? ? myfolder

[@samsid5223]

@houssem How can I enable csi blob driver for already created aks which is multinode cluster. I trued with az aks update command but it's not working for multinode cluster and recommending to try az aks nodepool update command.

[@ashwaqjaved1676]

az aks update --enable-blob-driver -n myAKSCluster -g myResourceGroup

[@NielMorgan-z8v]

Hi @houssem, thank you for this video it actually helped me got the blobfuse pv working as i could not get it working from the MS docs, I have an issue though that I hope you might be able to point me in a good direction. I have a specific blob storage account that is associated specifically for my kube cluster, but for this specific deployment I want the pvc and mount should only be able to read from the storage account or PV but not allowed to write. I have went as far as using ReadOnlyMany on both the pv and pvc, inclusing readOnly:true on the pv, but the pod is still able to create and delete files on the storage account, any suggestions? do you maybe have a discord to chat on?