Merge pull request #277052 from schaffererin/bug260955

Added CLI command to enable node autoprovisioning on an existing cluster

Author: Stacyrch140

articles/aks/node-autoprovision.md

@@ -4,7 +4,8 @@ description: Learn about Azure Kubernetes Service (AKS) node autoprovisioning (p
 ms.topic: article
 ms.custom: devx-track-azurecli
 ms.date: 01/18/2024
-ms.author: juda
+ms.author: schaffererin
+author: schaffererin
 #Customer intent: As a cluster operator or developer, how to scale my cluster based on workload requirements and right size my nodes automatically
 ---
 
@@ -68,7 +69,7 @@ NAP is based on the Open Source [Karpenter](https://karpenter.sh) project, and t
 - The only network configuration allowed is Cilium + Overlay + Azure
 - You can't enable in a cluster where node pools have cluster autoscaler enabled
 
-### Unsupported features:
+### Unsupported features
 
 - Windows node pools
 - Applying custom configuration to the node kubelet
@@ -84,69 +85,82 @@ NAP is based on the Open Source [Karpenter](https://karpenter.sh) project, and t
 
 ## Enable node autoprovisioning
 
-To enable node autoprovisioning, create a new cluster using the az aks create command and set --node-provisioning-mode to "Auto". You'll also need to use overlay networking and the cilium network policy.  
+### Enable node autoprovisioning on a new cluster
 
 ### [Azure CLI](#tab/azure-cli)
 
-```azurecli-interactive
-az aks create --name karpuktest --resource-group karpuk --node-provisioning-mode Auto --network-plugin azure --network-plugin-mode overlay --network-dataplane cilium
+- Enable node autoprovisioning on a new cluster using the `az aks create` command and set `--node-provisioning-mode` to `Auto`. You also need to set the `--network-plugin` to `azure`, `--network-plugin-mode` to `overlay`, and `--network-dataplane` to `cilium`.
 
-```
+    ```azurecli-interactive
+    az aks create --name $CLUSTER_NAME --resource-group $RESOURCE_GROUP_NAME --node-provisioning-mode Auto --network-plugin azure --network-plugin-mode overlay --network-dataplane cilium
+    ```
 
-### [Azure ARM](#tab/azure-arm)
+### [ARM template](#tab/arm)
 
-```azurecli-interactive
-az deployment group create --resource-group napcluster --template-file ./nap.json  
-```
+- Enable node autoprovisioning on a new cluster using the `az deployment group create` command and specify the `--template-file` parameter with the path to the ARM template file.
+
+    ```azurecli-interactive
+    az deployment group create --resource-group $RESOURCE_GROUP_NAME --template-file ./nap.json  
+    ```
 
-```arm
-{
-  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
-  "contentVersion": "1.0.0.0",
-  "metadata": {},
-  "parameters": {},
-  "resources": [
+    The `nap.json` file should contain the following ARM template:
+
+    ```JSON
     {
-      "type": "Microsoft.ContainerService/managedClusters",
-      "apiVersion": "2023-09-02-preview",
-      "sku": {
-        "name": "Base",
-        "tier": "Standard"
-      },
-      "name": "napcluster",
-      "location": "uksouth",
-      "identity": {
-        "type": "SystemAssigned"
-      },
-      "properties": {
-        "networkProfile": {
-            "networkPlugin": "azure",
-            "networkPluginMode": "overlay",
-            "networkPolicy": "cilium",
-            "networkDataplane":"cilium",
-            "loadBalancerSku": "Standard"
-        },
-        "dnsPrefix": "napcluster",
-        "agentPoolProfiles": [
-          {
-            "name": "agentpool",
-            "count": 3,
-            "vmSize": "standard_d2s_v3",
-            "osType": "Linux",
-            "mode": "System"
+      "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
+      "contentVersion": "1.0.0.0",
+      "metadata": {},
+      "parameters": {},
+      "resources": [
+        {
+          "type": "Microsoft.ContainerService/managedClusters",
+          "apiVersion": "2023-09-02-preview",
+          "sku": {
+            "name": "Base",
+            "tier": "Standard"
+          },
+          "name": "napcluster",
+          "location": "uksouth",
+          "identity": {
+            "type": "SystemAssigned"
+          },
+          "properties": {
+            "networkProfile": {
+                "networkPlugin": "azure",
+                "networkPluginMode": "overlay",
+                "networkPolicy": "cilium",
+                "networkDataplane":"cilium",
+                "loadBalancerSku": "Standard"
+            },
+            "dnsPrefix": "napcluster",
+            "agentPoolProfiles": [
+              {
+                "name": "agentpool",
+                "count": 3,
+                "vmSize": "standard_d2s_v3",
+                "osType": "Linux",
+                "mode": "System"
+              }
+            ],
+            "nodeProvisioningProfile": {
+              "mode": "Auto"
+            },
           }
-        ],
-        "nodeProvisioningProfile": {
-          "mode": "Auto"
-        },
-      }
+        }
+      ]
     }
-  ]
-}
-```
+    ```
 
 ---
 
+### Enable node autoprovisioning on an existing cluster
+
+- Enable node autoprovisioning on an existing cluster using the `az aks update` command and set `--node-provisioning-mode` to `Auto`. You also need to set the `--network-plugin` to `azure`, `--network-plugin-mode` to `overlay`, and `--network-dataplane` to `cilium`.
+
+    ```azurecli-interactive
+    az aks update --name $CLUSTER_NAME --resource-group $RESOURCE_GROUP_NAME --node-provisioning-mode Auto --network-plugin azure --network-plugin-mode overlay --network-dataplane cilium
+    ```
+
 ## Node pools
 
 Node autoprovision uses a list of VM SKUs as a starting point to decide which is best suited for the workloads that are in a pending state.  Having control over what SKU you want in the initial pool allows you to specify specific SKU families, or VM types and the maximum amount of resources a provisioner uses.