Let kubernetes be aware of data disk attachment limitations or make the limit "soft"
Currently there is a performance restraint on the data disks tied to a VM based on its size. https://blogs.technet.microsoft.com/uspartner_ts2team/2015/08/26/azure-vm-drive-attachment-limits/
It will be good to either transform this limit to a "soft", one raising alerts instead of blocking the attachment and/or let kubernetes know that this node cannot attach new disks in order to schedule pods to different nodes.
This issue has been resolved in k8s v1.12.0 by feature: Enable dynamic azure disk volume limits:
Before v1.12.0, the maximum disk number of node is always set as 16 by default, so if it’s a little VM size that only supports 8 disk attachment, there would be error after attaching the 9th disk, while from v1.12.0, the 9th disk would not be scheduled to that node if it only accepts 8 disks totally.