Skip to content

Commit e1b8ae9

Browse files
Update start-stop-cluster.md
adding again the note because still it is valid and many cxs asked about it
1 parent 7affe18 commit e1b8ae9

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

articles/aks/start-stop-cluster.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,10 @@ To better optimize your costs during these periods, you can turn off, or stop, y
1515
> [!CAUTION]
1616
> 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.
1717
18+
> [!NOTE]
19+
> AKS start operations will restore all objects from ETCD with the exception of standalone pods with the same names and ages. meaning that a pod's age will continue to be calculated from its original creation time. This count will keep increasing over time, regardless of whether the cluster is in a stopped state.
20+
21+
1822
## Before you begin
1923

2024
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)