You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Virtual Machines node pools is awesome. However, when multiple VM sizes or generations are mixed, an explanation is needed regarding the strategies and priorities used for allocation. Like this doc.
BTW, if, in cases where the stock of VM sizes or generations evaluated as having higher priority is depleted, the next highest priority is allocated instead, this would be an excellent feature. If so, please clearly state this in the documentation. Thanks!
Type of issue
Missing information
Feedback
Virtual Machines node pools is awesome. However, when multiple VM sizes or generations are mixed, an explanation is needed regarding the strategies and priorities used for allocation. Like this doc.
BTW, if, in cases where the stock of VM sizes or generations evaluated as having higher priority is depleted, the next highest priority is allocated instead, this would be an excellent feature. If so, please clearly state this in the documentation. Thanks!
Page URL
https://learn.microsoft.com/en-us/azure/aks/virtual-machines-node-pools#add-a-manual-scale-profile-to-a-node-pool
Content source URL
https://github.com/MicrosoftDocs/azure-aks-docs/blob/main/articles/aks/virtual-machines-node-pools.md
Author
@wdarko1
Document Id
5b8d05eb-273f-e369-a3f5-4c739008b3e3
The text was updated successfully, but these errors were encountered: