Skip to content

Commit e19e56f

Browse files
Merge pull request #248913 from MGoedtel/task63040
added Windows Node deallocate detail
2 parents 2d4aa09 + 2a50885 commit e19e56f

File tree

1 file changed

+12
-14
lines changed

1 file changed

+12
-14
lines changed

articles/aks/scale-down-mode.md

Lines changed: 12 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -3,14 +3,14 @@ title: Use Scale-down Mode for your Azure Kubernetes Service (AKS) cluster
33
titleSuffix: Azure Kubernetes Service
44
description: Learn how to use Scale-down Mode in Azure Kubernetes Service (AKS).
55
ms.topic: article
6-
ms.date: 09/01/2021
6+
ms.date: 08/21/2023
77
ms.author: qpetraroia
88
author: qpetraroia
99
---
1010

1111
# Use Scale-down Mode to delete/deallocate nodes in Azure Kubernetes Service (AKS)
1212

13-
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.
13+
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.
1414

1515
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][state-billing-azure-vm]. 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.
1616

@@ -24,16 +24,16 @@ This article assumes that you have an existing AKS cluster. If you need an AKS c
2424

2525
### Limitations
2626

27-
- [Ephemeral OS][ephemeral-os] disks aren't supported. Be sure to specify managed OS disks via `--node-osdisk-type Managed` when creating a cluster or node pool.
27+
- [Ephemeral OS][ephemeral-os] disks aren't supported. Be sure to specify managed OS disks by including the argument `--node-osdisk-type Managed` when creating a cluster or node pool.
2828

2929
> [!NOTE]
3030
> Previously, while Scale-down Mode was in preview, [spot node pools][spot-node-pool] were unsupported. Now that Scale-down Mode is Generally Available, this limitation no longer applies.
3131
3232
## Using Scale-down Mode to deallocate nodes on scale-down
3333

34-
By setting `--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.
34+
By setting `--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 are started first before any new nodes are provisioned.
3535

36-
In this example, we create a new node pool with 20 nodes and specify that upon scale-down, nodes are to be deallocated via `--scale-down-mode Deallocate`.
36+
In this example, we create a new node pool with 20 nodes and specify that upon scale-down, nodes are to be deallocated using the argument `--scale-down-mode Deallocate`.
3737

3838
```azurecli-interactive
3939
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
@@ -45,6 +45,12 @@ By scaling the node pool and changing the node count to 5, we'll deallocate 15 n
4545
az aks nodepool scale --node-count 5 --name nodepool2 --cluster-name myAKSCluster --resource-group myResourceGroup
4646
```
4747

48+
To deallocate Windows nodes during scale-down, run the following command. The default behavior is consistent with Linux nodes, where nodes are [deleted during scale-down](#using-scale-down-mode-to-delete-nodes-on-scale-down).
49+
50+
```azurecli-interactive
51+
az aks nodepool add --node-count 20 --scale-down-mode Deallocate --os-type Windows --node-osdisk-type Managed --max-pods 10 --name npwin2 --cluster-name myAKSCluster --resource-group myResourceGroup
52+
```
53+
4854
### Deleting previously deallocated nodes
4955

5056
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.
@@ -60,7 +66,7 @@ az aks nodepool update --scale-down-mode Delete --name nodepool2 --cluster-name
6066

6167
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 `--scale-down-mode Delete`.
6268

63-
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.
69+
In this example, we create a new node pool and specify that our nodes will be deleted upon scale-down using the argument `--scale-down-mode Delete`. Scaling operations will be handled using the cluster autoscaler.
6470

6571
```azurecli-interactive
6672
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
@@ -75,14 +81,6 @@ az aks nodepool add --enable-cluster-autoscaler --min-count 1 --max-count 10 --m
7581
[aks-quickstart-cli]: ./learn/quick-kubernetes-deploy-cli.md
7682
[aks-quickstart-portal]: ./learn/quick-kubernetes-deploy-portal.md
7783
[aks-quickstart-powershell]: ./learn/quick-kubernetes-deploy-powershell.md
78-
[aks-support-policies]: support-policies.md
79-
[aks-faq]: faq.md
80-
[az-extension-add]: /cli/azure/extension#az_extension_add
81-
[az-extension-update]: /cli/azure/extension#az_extension_update
82-
[az-feature-list]: /cli/azure/feature#az_feature_list
83-
[az-feature-register]: /cli/azure/feature#az_feature_register
84-
[az-aks-install-cli]: /cli/azure/aks#az_aks_install_cli
85-
[az-provider-register]: /cli/azure/provider#az_provider_register
8684
[aks-upgrade]: upgrade-cluster.md
8785
[cluster-autoscaler]: cluster-autoscaler.md
8886
[ephemeral-os]: concepts-storage.md#ephemeral-os-disk

0 commit comments

Comments
 (0)