add --generate-ssh-keys to az aks create calls

Author: tamram

articles/aks/azure-cni-overlay.md

@@ -250,7 +250,7 @@ The following attributes are provided to support dual-stack clusters:
         --network-plugin-mode overlay \
         --ip-families ipv4,ipv6 \
         --generate-ssh-keys
-      ```
+    ```
 
 ---
 

articles/aks/azure-cni-powered-by-cilium.md

@@ -73,11 +73,15 @@ Azure CNI powered by Cilium currently has the following limitations:
 Use the following commands to create a cluster with an overlay network and Cilium. Replace the values for `<clusterName>`, `<resourceGroupName>`, and `<location>`:
 
 ```azurecli-interactive
-az aks create --name <clusterName> --resource-group <resourceGroupName> --location <location> \
-  --network-plugin azure \
-  --network-plugin-mode overlay \
-  --pod-cidr 192.168.0.0/16 \
-  --network-dataplane cilium
+az aks create \
+    --name <clusterName> \
+    --resource-group <resourceGroupName> \
+    --location <location> \
+    --network-plugin azure \
+    --network-plugin-mode overlay \
+    --pod-cidr 192.168.0.0/16 \
+    --network-dataplane cilium \
+    --generate-ssh-keys
 ```
 
 > [!NOTE]
@@ -102,12 +106,16 @@ az network vnet subnet create --resource-group <resourceGroupName> --vnet-name <
 Create the cluster using `--network-dataplane cilium`:
 
 ```azurecli-interactive
-az aks create --name <clusterName> --resource-group <resourceGroupName> --location <location> \
-  --max-pods 250 \
-  --network-plugin azure \
-  --vnet-subnet-id /subscriptions/<subscriptionId>/resourceGroups/<resourceGroupName>/providers/Microsoft.Network/virtualNetworks/<vnetName>/subnets/nodesubnet \
-  --pod-subnet-id /subscriptions/<subscriptionId>/resourceGroups/<resourceGroupName>/providers/Microsoft.Network/virtualNetworks/<vnetName>/subnets/podsubnet \
-  --network-dataplane cilium
+az aks create \
+    --name <clusterName> \
+    --resource-group <resourceGroupName> \
+    --location <location> \
+    --max-pods 250 \
+    --network-plugin azure \
+    --vnet-subnet-id /subscriptions/<subscriptionId>/resourceGroups/<resourceGroupName>/providers/Microsoft.Network/virtualNetworks/<vnetName>/subnets/nodesubnet \
+    --pod-subnet-id /subscriptions/<subscriptionId>/resourceGroups/<resourceGroupName>/providers/Microsoft.Network/virtualNetworks/<vnetName>/subnets/podsubnet \
+    --network-dataplane cilium \
+    --generate-ssh-keys
 ```
 
 ## Upgrade an existing cluster to Azure CNI Powered by Cilium

articles/aks/azure-hybrid-benefit.md

@@ -30,7 +30,15 @@ PASSWORD='tempPassword1234$'
 RG_NAME='myResourceGroup'
 CLUSTER='myAKSCluster'
 
-az aks create --resource-group $RG_NAME --name $CLUSTER --load-balancer-sku Standard --network-plugin azure --windows-admin-username azure --windows-admin-password $PASSWORD --enable-ahub
+az aks create \
+    --resource-group $RG_NAME \
+    --name $CLUSTER \
+    --load-balancer-sku Standard \
+    --network-plugin azure \
+    --windows-admin-username azure \
+    --windows-admin-password $PASSWORD \
+    --enable-ahub \
+    --generate-ssh-keys
 ```
 
 To enable Azure Hybrid Benefit on an existing AKS cluster:

articles/aks/best-practices-app-cluster-reliability.md

@@ -348,7 +348,16 @@ To keep up with application demands in AKS, you might need to adjust the number
 You can use the `--enable-cluster-autoscaler` parameter when creating an AKS cluster to enable the cluster autoscaler, as shown in the following example:
 
 ```azurecli-interactive
-az aks create --resource-group myResourceGroup --name myAKSCluster --node-count 2 --vm-set-type VirtualMachineScaleSets --load-balancer-sku standard --enable-cluster-autoscaler  --min-count 1 --max-count 3
+az aks create \
+    --resource-group myResourceGroup \
+    --name myAKSCluster \
+    --node-count 2 \
+    --vm-set-type VirtualMachineScaleSets \
+    --load-balancer-sku standard \
+    --enable-cluster-autoscaler  \
+    --min-count 1 \
+    --max-count 3 \
+    --generate-ssh-keys
 ```
 
 You can also enable the cluster autoscaler on an existing node pool and configure more granular details of the cluster autoscaler by changing the default values in the cluster-wide autoscaler profile.

articles/aks/cluster-autoscaler.md

@@ -43,7 +43,8 @@ This article requires Azure CLI version 2.0.76 or later. Run `az --version` to f
     --load-balancer-sku standard \
     --enable-cluster-autoscaler \
     --min-count 1 \
-    --max-count 3
+    --max-count 3 \
+    --generate-ssh-keys
     ```
 
     It takes a few minutes to create the cluster and configure the cluster autoscaler settings.
@@ -178,13 +179,14 @@ The following table lists the available settings for the cluster autoscaler prof
 
     ```azurecli-interactive
     az aks create \
-      --resource-group myResourceGroup \
-      --name myAKSCluster \
-      --node-count 1 \
-      --enable-cluster-autoscaler \
-      --min-count 1 \
-      --max-count 3 \
-      --cluster-autoscaler-profile scan-interval=30s
+        --resource-group myResourceGroup \
+        --name myAKSCluster \
+        --node-count 1 \
+        --enable-cluster-autoscaler \
+        --min-count 1 \
+        --max-count 3 \
+        --cluster-autoscaler-profile scan-interval=30s \
+        --generate-ssh-keys
     ```
 
 ### Set the cluster autoscaler profile on an existing cluster

articles/aks/concepts-clusters-workloads.md

@@ -233,7 +233,11 @@ When you create an AKS cluster, you specify an Azure resource group to create th
 The node resource group is assigned a name by default with the following format: *MC_resourceGroupName_clusterName_location*. During cluster creation, you can specify the name assigned to your node resource group. When using an Azure Resource Manager template, you can define the name using the `nodeResourceGroup` property. When using Azure CLI, you use the `--node-resource-group` parameter with the `az aks create` command, as shown in the following example:
 
 ```azurecli-interactive
-az aks create --name myAKSCluster --resource-group myResourceGroup --node-resource-group myNodeResourceGroup
+az aks create \
+    --name myAKSCluster \
+    --resource-group myResourceGroup \
+    --node-resource-group myNodeResourceGroup \
+    --generate-ssh-keys
 ```
 
 When you delete your AKS cluster, the AKS resource provider automatically deletes the node resource group.

articles/aks/configure-azure-cni-dynamic-ip-allocation.md

@@ -94,13 +94,17 @@ Create the cluster, referencing the node subnet using `--vnet-subnet-id` and the
 CLUSTER_NAME="myAKSCluster"
 SUBSCRIPTION="aaaaaaa-aaaaa-aaaaaa-aaaa"
 
-az aks create --name $CLUSTER_NAME --resource-group $RESOURCE_GROUP_NAME --location $LOCATION \
+az aks create \
+    --name $CLUSTER_NAME \
+    --resource-group $RESOURCE_GROUP_NAME \
+    --location $LOCATION \
     --max-pods 250 \
     --node-count 2 \
     --network-plugin azure \
     --vnet-subnet-id /subscriptions/$SUBSCRIPTION/resourceGroups/$RESOURCE_GROUP_NAME/providers/Microsoft.Network/virtualNetworks/$VNET_NAME/subnets/$SUBNET_NAME_1 \
     --pod-subnet-id /subscriptions/$SUBSCRIPTION/resourceGroups/$RESOURCE_GROUP_NAME/providers/Microsoft.Network/virtualNetworks/$VNET_NAME/subnets/$SUBNET_NAME_2 \
-    --enable-addons monitoring
+    --enable-addons monitoring \
+    --generate-ssh-keys
 ```
 
 ### Adding node pool

articles/aks/configure-azure-cni-static-block-allocation.md

@@ -160,15 +160,19 @@ Create the cluster, referencing the node subnet using `--vnet-subnet-id`, the po
 clusterName="myAKSCluster"
 subscription="aaaaaaa-aaaaa-aaaaaa-aaaa"
 
-az aks create --name $clusterName --resource-group $resourceGroup --location $location \
+az aks create \
+    --name $clusterName \
+    --resource-group $resourceGroup \
+    --location $location \
     --max-pods 250 \
     --node-count 2 \
     --network-plugin azure \
     --pod-ip-allocation-mode StaticBlock \
     --vnet-subnet-id /subscriptions/$subscription/resourceGroups/$resourceGroup/providers/Microsoft.Network/virtualNetworks/$vnet/subnets/nodesubnet \
     --pod-subnet-id /subscriptions/$subscription/resourceGroups/$resourceGroup/providers/Microsoft.Network/virtualNetworks/$vnet/subnets/podsubnet \
     --enable-addons monitoring \
-    --kubernetes-version 1.28
+    --kubernetes-version 1.28 \
+    --generate-ssh-keys
 ```
 
 ### Adding node pool

articles/aks/configure-kube-proxy.md

@@ -110,10 +110,17 @@ You can view the full `kube-proxy` configuration structure in the [AKS Cluster S
 
     ```azurecli-interactive
     # Create a new cluster
-    az aks create --resource-group <resourceGroup> --name <clusterName> --kube-proxy-config kube-proxy.json
+    az aks create \
+        --resource-group <resourceGroup> \
+        --name <clusterName> \
+        --kube-proxy-config kube-proxy.json \
+        --generate-ssh-keys
 
     # Update an existing cluster
-    az aks update --resource-group <resourceGroup> --name <clusterName> --kube-proxy-config kube-proxy.json
+    az aks update \
+        --resource-group <resourceGroup> \
+        --name <clusterName> \
+        --kube-proxy-config kube-proxy.json
     ```
 
 ## Next steps

articles/aks/configure-kubenet-dual-stack.md

@@ -77,7 +77,12 @@ The following attributes are provided to support dual-stack clusters:
 2. Create a dual-stack AKS cluster using the [`az aks create`][az-aks-create] command with the `--ip-families` parameter set to `ipv4,ipv6`.
 
     ```azurecli-interactive
-    az aks create --location <region> --resource-group <resourceGroupName> --name <clusterName> --ip-families ipv4,ipv6
+    az aks create \
+        --location <region> \
+        --resource-group <resourceGroupName> \
+        --name <clusterName> \
+        --ip-families ipv4,ipv6 \
+        --generate-ssh-keys
     ```
 
 3. Once the cluster is created, get the cluster admin credentials using the [`az aks get-credentials`][az-aks-get-credentials] command.