AKS
AKS copied to clipboard
Nodepool stop or start delete nodes in scaleDownMode "Deallocate"
What happened: We use 2 preview features on some nodepools:
- scale down mode "deallocate" https://docs.microsoft.com/en-us/azure/aks/scale-down-mode
- nodepool stop/start https://docs.microsoft.com/en-us/azure/aks/start-stop-nodepools
When starting or stopping the nodepool, existing VMSS instances (running or deallocated) are deleted.
What you expected to happen: Stopping nodepool should deallocate running VMSS instances instead of deleting them. Starting nodepool should not affect VMSS instances and let autoscaler start existing instances or create new ones if needed.
How to reproduce it (as minimally and precisely as possible):
- Create a nodepool with scaledown mode set to "deallocate" and autoscaler (min nodes = 0) enabled.
- Run
az aks nodepool stop
oraz aks nodepool start
Anything else we need to know?: Azure Support has confirmed the issue and advised to open an issue here as we're using preview features.
Environment:
- Kubernetes version (use
kubectl version
): 1.21.7 - Size of cluster (how many worker nodes are in the cluster?): varies from 0 to ~5
- General description of workloads in the cluster (e.g. HTTP microservices, Java app, Ruby on Rails, machine learning, etc.): ephemeral test environnements
- Others:
Hi alk-jozog, 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!
Triage required from @Azure/aks-pm
Action required from @Azure/aks-pm
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
@qpetraroia can you take a look?
Action required from @Azure/aks-pm
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads