AKS
AKS copied to clipboard
Azure
[Feature] Premium SSD v2 resource validation for supported nodepools
Is your feature request related to a problem? Please describe. Per this documentation :
Currently, Premium SSD v2 disks can only be attached to zonal VMs.
I experienced a situation where I accidentally created an AKS PV on a non-zonal nodepool and AKS created the PV resource, volumeAttachment, and a Premium SSD v2 disk. The Premium SSD v2 disk was reported by the Azure API as attached to the un-supported VM. I could not unattach and delete the Premium SSD v2 disk until I scaled the AKS nodepool down and back up until AKS eliminated the node (luckily it was the last instance ID in the nodepool) and spun up a new one - this was after restarting the affected node and attempting to reimage it. This also affected other persistentVolumes attached to the same node that were not Premium SSD v2 disks, they were unable to mount their pods and the description of the volumeAttachments corresponding to them was an error referencing the erroneously added Premium SSD v2 disk.
Describe the solution you'd like While I acknowledge I made the initial mistake of creating a PV spec for a Premium SSD v2 disk on a state unsupported nodepool, I can't imagine I'll be the last person to make the same mistake while this limitation regarding zonal VMs exists. I would request that there be some sort of resource validation before AKS creates the PV resource (and subsequently creates the Azure disk) on an unsupported node.
Describe alternatives you've considered N/A
Additional context Premium SSD v2's work correctly as persistentVolumes on zonal VMs.
![microsoft-github-policy-service[bot] avatar](https://avatars.githubusercontent.com/in/95686?v=4 "Published by a pub.dev verified publisher"){kind=small}
This issue has been automatically marked as stale because it has not had any activity for 180 days. It will be closed if no further activity occurs within 7 days of this comment. @yuemlu