Max Data Disks attached to a worker node in Azure

Hello @Soundarya Ayyappan , To answer your question "YES". Here is the brief explanation:

For Azure Disks :-

Azure Disks are more specifically attached to the corresponding nodes. When you create a PVC followed by a POD then a data disk will be attached to the corresponding worker node on which that POD was deployed. Since for D4a_v4 SKU VMs we can attach only 8 data disks hence you can create only 8 PVCs.

Please Note: - Once you create 9th PVC - if the cluster-autoscaler is enabled it will add a new node and new data disk will be added to the new node once the POD gets created.

Something like below:-

Events: Type Reason Age From Message

Normal TriggeredScaleUp 36s cluster-autoscaler pod triggered scale-up: [{aks-agentpool-40625907-vmss 2->3 (max: 5)}] Warning FailedScheduling 15s (x3 over 39s) default-scheduler 0/2 nodes are available: 2 node(s) exceed max volume count.

For Azure files: When you create a PVC using Azure files , when a corresponding POD gets created a storage account will be created dynamically (if you are not using the existing storage account) and then file share will be mounted in that storage account. You can create any number of PVCs using the azure files share and there is no limit - it depends on the storage account provider capacity

To summarize, basically the thing which we need to understand is:

1. Azure Disks is dependent on the corresponding VM SKU ( i.e. worker node VM Size)
2. Azure Files is independent of the corresponding VM SKU (it depends on the external storage account)

Hope that clarifies your query. Kindly let us know if you have additional questions.

Please make sure to "Upvote & Accept the answer" so that it will be helpful to the community out there who are looking for similar ones.

Regards, Shiva.