<p>I'm trying to run different helm charts and I keep running into this error. It's much more cost effective for me to run 3-4 cheaper nodes than 1 or 2 very expensive nodes that can have more disks attached to them.</p>

<p>Is there a way to configure kubernetes or helm to have a disk attach limit or to set the affinity of one deployment to a particular node?</p>

<p>It's very frustrating that all the deployments try to attach to one node and then run out of disk attach quota.</p>

<p>Here is the error:</p>

<blockquote>
  <p>Service returned an error. Status=409 Code="OperationNotAllowed"
  Message="The maximum number of data disks allowed to be attached to a
  VM of this size is 4."</p>
</blockquote>

<blockquote>
  <p>Is there a way to configure kubernetes or helm to have a disk attach
  limit or to set the affinity of one deployment to a particular node?</p>
</blockquote>

<p>For now, ACS k8s provision PVC based on Azure managed disks or blob disks, so the limit is the number of VM disks.</p>

<p>For now, Azure does not support change the limit about number of VM disks. About VM size and max data disks, we can find the limit here:
<a href="https://i.stack.imgur.com/VwkhY.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/VwkhY.png" alt="enter image description here"></a></p>

<p>More information about limit, please refer to this <a href="https://learn.microsoft.com/en-us/azure/virtual-machines/windows/sizes-memory" rel="nofollow noreferrer">link</a>.</p>

<p>By the way, the disk maximum capacity is <strong>2TB</strong>, maybe we can extend it to 2TB.</p>
