Skip to content

Commit a27ddf3

Browse files
Merge pull request #276993 from axelgMS/patch-59
Update start-stop-nodepools.md
2 parents 21ee526 + badcb94 commit a27ddf3

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

articles/aks/start-stop-nodepools.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,7 @@ You might not need to continuously run your AKS workloads. For example, you migh
1919
* The cluster and node pool must be running.
2020
* You can't stop node pools from clusters which use the [Node Autoprovisioning (NAP)](node-autoprovision.md) feature.
2121

22+
2223
## Before you begin
2324

2425
This article assumes you have an existing AKS cluster. If you need an AKS cluster, create one using the [Azure CLI][aks-quickstart-cli], [Azure PowerShell][aks-quickstart-powershell], or the [Azure portal][aks-quickstart-portal].
@@ -56,6 +57,10 @@ This article assumes you have an existing AKS cluster. If you need an AKS cluste
5657
> [!NOTE]
5758
> If the `provisioningState` shows `Stopping`, your node pool is still in the process of stopping.
5859
60+
61+
> [!NOTE]
62+
> Stopping the node pool will stop its Cluster Autoscaler, and starts it back when starting the node pool. So if you manually modify the number of VMSS instances in the pool while it's stopped, Cluster Autoscaler might show inconsistencies.
63+
5964
---
6065
6166
## Start a stopped AKS node pool

0 commit comments

Comments
 (0)