# Welcome to the Azure Kubernetes Service on Azure Stack HCI repo This is where the AKS-HCI team will track features and issues with AKS-HCI. We will monitor this repo in order to engage with our community and discuss questions, customer scenarios, or feature requests. Checkout our projects tab to see the roadmap for AKS-HCI!
MIT License
109
stars
45
forks
source link
Allow scaling down nodepools in 'out-of-capacity' situations #349
Allow scaling down nodepools in 'out-of-capacity' situations during 'Update-AksHci':
Description:
If I have a cluster with too less memory left to create a new VM and start an Update-AksHci - the update will start but wait in an out-of-capacity loop until there is enough memory freed up to create a new VM.
One option is to scale down a nodepool, but scaling a nodepool is blocked in this situation:
Second option is to delete a nodepool, what succeeded and Update-AksHci continued.
Feature Request:
Please allow scaling down nodepools in out-of-capacity situations. We do not have anytime multiple nodepools available, where we can easily delete one, in case we run into an update hang because of running out of resources.
Allow scaling down nodepools in 'out-of-capacity' situations during 'Update-AksHci':
Description: If I have a cluster with too less memory left to create a new VM and start an
Update-AksHci- the update will start but wait in an out-of-capacity loop until there is enough memory freed up to create a new VM.One option is to scale down a nodepool, but scaling a nodepool is blocked in this situation:
Second option is to delete a nodepool, what succeeded and
Update-AksHcicontinued.Feature Request: Please allow scaling down nodepools in out-of-capacity situations. We do not have anytime multiple nodepools available, where we can easily delete one, in case we run into an update hang because of running out of resources.