Use Scale-down Mode to delete/deallocate nodes in Azure Kubernetes Service (AKS)
By default, scale-up operations performed manually or by the cluster autoscaler require the allocation and provisioning of new nodes, and scale-down operations delete nodes. Scale-down Mode allows you to decide whether you would like to delete or deallocate the nodes in your Azure Kubernetes Service (AKS) cluster upon scaling down.
When an Azure VM is in the
Stopped (deallocated) state, you will not be charged for the VM compute resources. However, you'll still need to pay for any OS and data storage disks attached to the VM. This also means that the container images will be preserved on those nodes. For more information, see States and billing of Azure Virtual Machines. This behavior allows for faster operation speeds, as your deployment uses cached images. Scale-down Mode removes the need to pre-provision nodes and pre-pull container images, saving you compute cost.
Before you begin
In order to preserve any deallocated VMs, you must set Scale-down Mode to Deallocate. That includes VMs that have been deallocated using IaaS APIs (Virtual Machine Scale Set APIs). Setting Scale-down Mode to Delete will remove any deallocate VMs. Once applied the deallocated mode and scale down operation occured, those nodes keep registered in APIserver and appear as NotReady state.
This article assumes that you have an existing AKS cluster. If you need an AKS cluster, see the AKS quickstart using the Azure CLI, using Azure PowerShell, or using the Azure portal.
- Ephemeral OS disks aren't supported. Be sure to specify managed OS disks via
--node-osdisk-type Managedwhen creating a cluster or node pool.
Previously, while Scale-down Mode was in preview, spot node pools were unsupported. Now that Scale-down Mode is Generally Available, this limitation no longer applies.
Using Scale-down Mode to deallocate nodes on scale-down
--scale-down-mode Deallocate, nodes will be deallocated during a scale-down of your cluster/node pool. All deallocated nodes are stopped. When your cluster/node pool needs to scale up, the deallocated nodes will be started first before any new nodes are provisioned.
In this example, we create a new node pool with 20 nodes and specify that upon scale-down, nodes are to be deallocated via
az aks nodepool add --node-count 20 --scale-down-mode Deallocate --node-osdisk-type Managed --max-pods 10 --name nodepool2 --cluster-name myAKSCluster --resource-group myResourceGroup
By scaling the node pool and changing the node count to 5, we'll deallocate 15 nodes.
az aks nodepool scale --node-count 5 --name nodepool2 --cluster-name myAKSCluster --resource-group myResourceGroup
Deleting previously deallocated nodes
To delete your deallocated nodes, you can change your Scale-down Mode to
Delete by setting
--scale-down-mode Delete. The 15 deallocated nodes will now be deleted.
az aks nodepool update --scale-down-mode Delete --name nodepool2 --cluster-name myAKSCluster --resource-group myResourceGroup
Changing your scale-down mode from
Delete then back to
Deallocate will delete all deallocated nodes while keeping your node pool in
Deallocate scale-down mode.
Using Scale-down Mode to delete nodes on scale-down
The default behavior of AKS without using Scale-down Mode is to delete your nodes when you scale-down your cluster. With Scale-down Mode, this behavior can be explicitly achieved by setting
In this example, we create a new node pool and specify that our nodes will be deleted upon scale-down via
--scale-down-mode Delete. Scaling operations will be handled via the cluster autoscaler.
az aks nodepool add --enable-cluster-autoscaler --min-count 1 --max-count 10 --max-pods 10 --node-osdisk-type Managed --scale-down-mode Delete --name nodepool3 --cluster-name myAKSCluster --resource-group myResourceGroup
- To learn more about upgrading your AKS cluster, see Upgrade an AKS cluster
- To learn more about the cluster autoscaler, see Automatically scale a cluster to meet application demands on AKS
Submit and view feedback for