Skip to content

Commit afe5512

Browse files
authored
Merge pull request #207821 from SreejaBhattacharya-MSFT/patch-37
Minor doc update
2 parents 5123ab7 + 6269eee commit afe5512

File tree

1 file changed

+0
-3
lines changed

1 file changed

+0
-3
lines changed

articles/aks/use-system-pools.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -104,9 +104,6 @@ New-AzAksCluster -ResourceGroupName myResourceGroup -Name myAKSCluster -NodeCoun
104104

105105
### [Azure CLI](#tab/azure-cli)
106106

107-
> [!Important]
108-
> You can't change node taints through the CLI after the node pool is created.
109-
110107
You can add one or more system node pools to existing AKS clusters. It's recommended to schedule your application pods on user node pools, and dedicate system node pools to only critical system pods. This prevents rogue application pods from accidentally killing system pods. Enforce this behavior with the `CriticalAddonsOnly=true:NoSchedule` [taint][aks-taints] for your system node pools.
111108

112109
The following command adds a dedicated node pool of mode type system with a default count of three nodes.

0 commit comments

Comments
 (0)