Open msebrenes opened 1 year ago
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
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Is your feature request related to a problem? Please describe. Having the option to isolate one node in a node pool from scaling actions.
Describe the solution you'd like In certain scenarios the option of isolating a particular node (from scaling down) to keep a specific workload running would be a great feature to have.
Describe alternatives you've considered There are no real alternatives as creating additional node pools for example, would require an extra charge that can be easily prevented by this feature.
Additional context A similar option already exists in other cloud services, and Azure have one similar feature for VMSS, which can be seen as an opportunity to implement into the AKS offering without creating the whole login from scratch.
Azure VMSS custom scale-in policies: https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-scale-in-policy#instance-protection-and-scale-in-policy