ghost
commented
3 years ago Hi ChiragPavecha, 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: 1) If this case is urgent, please open a Support Request so that our 24/7 support team may help you faster. 2) Please abide by the AKS repo Guidelines and Code of Conduct. 3) If you're having an issue, could it be described on the AKS Troubleshooting guides or AKS Diagnostics? 4) Make sure your subscribed to the AKS Release Notes to keep up to date with all that's new on AKS. 5) 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. 6) If you have a question, do take a look at our AKS FAQ. We place the most common ones there!
seguler
rouke-broersma
miwithro
paulgmiller
microsoft-github-policy-service[bot]
whywhy36
Support selection of nodes to remove when scaling down.
At the moment when you scale down, the oldest nodes will always stay and the newer nodes will be removed. Would be a nice feature to be able to remove a selected node when scaling down or maybe manually.
This will enable customers to remove an unhealthy node which is otherwise impacting the entire cluster.
Read more user scenarios here - https://feedback.azure.com/forums/914020-azure-kubernetes-service-aks/suggestions/35702938-support-selection-of-nodes-to-remove-when-scaling
What happened: It often happens that a specific node within a cluster is unhealthy (for various reasons) but there is no way to get rid of that specific node.
What you expected to happen: Have the ability to remove selected nodes within the AKS cluster