Skip to content

Commit dbbdb4f

Browse files
committed
added caution to start stop
1 parent 7ba26ca commit dbbdb4f

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

articles/aks/start-stop-cluster.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,9 @@ You may not need to continuously run your Azure Kubernetes Service (AKS) workloa
1212

1313
To better optimize your costs during these periods, you can turn off, or stop, your cluster. This action stops your control plane and agent nodes, allowing you to save on all the compute costs, while maintaining all objects except standalone pods. The cluster state is stored for when you start it again, allowing you to pick up where you left off.
1414

15+
> [!CAUTION]
16+
> Stopping your cluster deallocates the control plane and releases the capacity. In regions experiencing capacity constraints, customers may be unable to start a stopped cluster. We do not recommend stopping mission critical workloads for this reason.
17+
1518
## Before you begin
1619

1720
This article assumes you have an existing AKS cluster. If you need an AKS cluster, you can create one using [Azure CLI][aks-quickstart-cli], [Azure PowerShell][aks-quickstart-powershell], or the [Azure portal][aks-quickstart-portal].

0 commit comments

Comments
 (0)