AKS
AKS copied to clipboard
Azure
AKS nodepool vertical scaling
What happened: Today when a customer creates a node pool in AKS they are only able to scale that node pool horizontally. Many customers in their initial PoC a development phases will spin up these node pools in a SKU that is selected to be cost effective. Customer often want the ability to fine to the performance during development and as part of that they want to be able to change the SKU size of a deployed node pool. Currently to do this a customer has to go through the process of creating a new node pool with the SKU they want to test and destroy their old node pool. This can be a laborious process for customers especially when they need to repeatedly test performance on workloads to find the appropriate SKU.
What you expected to happen: Allow vertical scaling for node pools without having to destroy and recreate a node pool.
Hi naioja, AKS bot here :wave: Thank you for posting on the AKS Repo, I'll do my best to get a kind human from the AKS team to assist you.
I might be just a bot, but I'm told my suggestions are normally quite good, as such:
- If this case is urgent, please open a Support Request so that our 24/7 support team may help you faster.
- Please abide by the AKS repo Guidelines and Code of Conduct.
- If you're having an issue, could it be described on the AKS Troubleshooting guides or AKS Diagnostics?
- Make sure your subscribed to the AKS Release Notes to keep up to date with all that's new on AKS.
- Make sure there isn't a duplicate of this issue already reported. If there is, feel free to close this one and '+1' the existing issue.
- If you have a question, do take a look at our AKS FAQ. We place the most common ones there!
Definitely would love this. Having to create a new nodepool and move deployments, then delete the nodepool, etc. just seems unnecessary when its just a VM scale set under-the-hood, and those can be resized.
It would be nice feature to have like we have for VMs on Azure
just seems unnecessary when its just a VM scale set under-the-hood, and those can be resized.
for context, I believe resizing a VMSS does require scaling to zero/deallocating all VMs in some edge cases (and it's not possible to determine when you hit those edge cases until you error out) https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-upgrade-scale-set#properties-that-require-deallocation-to-change
Just stumbled accross this old issue, and I think it is already implemented but not really documented.
I tried vertically scaling the Default Nodepool yesterday with a Terraform deployment. I needed to set 'temporary_name_for_rotation' to support it, but overall it was recreating the Node Pool after changing the VM size without any issues. Behaviour is similar to a Cluster Upgrade.
Therefore, I guess this issue is resolved, but should be documented somewhere.
@XristophD I believe what happened with your terraform code was that it changed the size of VMS for the entire nodepool by creating either a new nodepool or just rebuilding one VM at a time - both being possible with uniform VMSS. Whereas with VMSS flex you can migrate the memory of a running VM and change the size "in-place" https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-orchestration-modes#what-has-changed-with-flexible-orchestration-mode for now this new type of VMSS is not supported for AKS.
Good Morning AKS Team,
Can we have a update on this Feature Request?
![microsoft-github-policy-service[bot] avatar](https://avatars.githubusercontent.com/in/95686?v=4 "Published by a pub.dev verified publisher"){kind=small}
