<p>I read that there is a limitation to the amount of data disks that can bound to a node in a cluster. Right now im using a small node which can only hold up to 4 data disks. If i exceed this amount i will get this error: <code>0/1 nodes are available: 1 node(s) exceed max volume count.</code></p>

<p>The question that i mainly have is how to handle this. I have some apps that just need a small amount of persistant storage in my cluster however i can only attach a few data disks. If i bind 4 data disks of 100m i already reached the max limit.</p>

<p>Could someone advice me on how to handle these scenarios? I can easily scale up the machines and i will have more power in my machine and more disks however the ratio disks vs server power is completely offset at that point.</p>

<p>Best
Pim</p>

Dirkos
<p>You should look at using Azure File instead of Azure Disk.  With Azure File, you can do ReadWriteMany hence having a single mount on the VM(node) to allow multiple POD to access the mounted volume. </p>

<p><a href="https://github.com/kubernetes/examples/blob/master/staging/volumes/azure_file/README.md" rel="nofollow noreferrer">https://github.com/kubernetes/examples/blob/master/staging/volumes/azure_file/README.md</a></p>

<p><a href="https://kubernetes.io/docs/concepts/storage/storage-classes/#azure-file" rel="nofollow noreferrer">https://kubernetes.io/docs/concepts/storage/storage-classes/#azure-file</a></p>

<p><a href="https://learn.microsoft.com/en-us/azure/aks/azure-files-dynamic-pv" rel="nofollow noreferrer">https://learn.microsoft.com/en-us/azure/aks/azure-files-dynamic-pv</a></p>
