Merge pull request #277234 from tamram/tamram24-0604

[SCOPED] add --generate-ssh-keys to az aks create calls

Author: AnnaMHuff

articles/aks/ai-toolchain-operator.md

@@ -96,7 +96,8 @@ The following sections describe how to create an AKS cluster with the AI toolcha
         --resource-group ${AZURE_RESOURCE_GROUP} \
         --name ${CLUSTER_NAME} \
         --enable-oidc-issuer \
-        --enable-ai-toolchain-operator
+        --enable-ai-toolchain-operator \
+        --generate-ssh-keys
     ```
 
     > [!NOTE]

articles/aks/aks-migration.md

@@ -72,14 +72,15 @@ The following example creates an AKS cluster with single node pool backed by a v
 
     ```azurecli-interactive
     az aks create \
-      --resource-group myResourceGroup \
-      --name myAKSCluster \
-      --node-count 1 \
-      --vm-set-type VirtualMachineScaleSets \
-      --load-balancer-sku standard \
-      --enable-cluster-autoscaler \
-      --min-count 1 \
-      --max-count 3
+        --resource-group myResourceGroup \
+        --name myAKSCluster \
+        --node-count 1 \
+        --vm-set-type VirtualMachineScaleSets \
+        --load-balancer-sku standard \
+        --enable-cluster-autoscaler \
+        --min-count 1 \
+        --max-count 3 \
+        --generate-ssh-keys
     ```
 
 ## Existing attached Azure Services

articles/aks/api-server-vnet-integration.md

@@ -87,7 +87,8 @@ You can configure your AKS clusters with API Server VNet Integration in managed
         --resource-group <resource-group> \
         --location <location> \
         --network-plugin azure \
-        --enable-apiserver-vnet-integration
+        --enable-apiserver-vnet-integration \
+        --generate-ssh-keys
     ```
 
 ### Deploy a private cluster
@@ -100,7 +101,8 @@ You can configure your AKS clusters with API Server VNet Integration in managed
         --location <location> \
         --network-plugin azure \
         --enable-private-cluster \
-        --enable-apiserver-vnet-integration
+        --enable-apiserver-vnet-integration \
+        --generate-ssh-keys
     ```
 
 ## Create a private AKS cluster with API Server VNet Integration using bring-your-own VNet
@@ -180,13 +182,14 @@ az group create --location <location> --name <resource-group>
 
     ```azurecli-interactive
     az aks create --name <cluster-name> \
-    --resource-group <resource-group> \
-    --location <location> \
-    --network-plugin azure \
-    --enable-apiserver-vnet-integration \
-    --vnet-subnet-id <cluster-subnet-resource-id> \
-    --apiserver-subnet-id <apiserver-subnet-resource-id> \
-    --assign-identity <managed-identity-resource-id>
+        --resource-group <resource-group> \
+        --location <location> \
+        --network-plugin azure \
+        --enable-apiserver-vnet-integration \
+        --vnet-subnet-id <cluster-subnet-resource-id> \
+        --apiserver-subnet-id <apiserver-subnet-resource-id> \
+        --assign-identity <managed-identity-resource-id> \
+        --generate-ssh-keys
     ```
 
 ### Deploy a private cluster
@@ -202,7 +205,8 @@ az group create --location <location> --name <resource-group>
     --enable-apiserver-vnet-integration \
     --vnet-subnet-id <cluster-subnet-resource-id> \
     --apiserver-subnet-id <apiserver-subnet-resource-id> \
-    --assign-identity <managed-identity-resource-id>
+    --assign-identity <managed-identity-resource-id> \
+    --generate-ssh-keys
     ```
 
 ## Convert an existing AKS cluster to API Server VNet Integration

articles/aks/app-routing.md

@@ -54,7 +54,12 @@ With the retirement of [Open Service Mesh][open-service-mesh-docs] (OSM) by the
 To enable application routing on a new cluster, use the [`az aks create`][az-aks-create] command, specifying the `--enable-app-routing` flag.
 
 ```azurecli-interactive
-az aks create --resource-group <ResourceGroupName> --name <ClusterName> --location <Location> --enable-app-routing
+az aks create \
+    --resource-group <ResourceGroupName> \
+    --name <ClusterName> \
+    --location <Location> \
+    --enable-app-routing \
+    --generate-ssh-keys
 ```
 
 ### Enable on an existing cluster
@@ -79,7 +84,13 @@ The following add-ons are required to support this configuration:
 Enable application routing on a new AKS cluster using the [`az aks create`][az-aks-create] command specifying the `--enable-app-routing` flag and the `--enable-addons` parameter with the `open-service-mesh` add-on:
 
 ```azurecli-interactive
-az aks create --resource-group <ResourceGroupName> --name <ClusterName> --location <Location> --enable-app-routing --enable-addons open-service-mesh 
+az aks create \
+    --resource-group <ResourceGroupName> \
+    --name <ClusterName> \
+    --location <Location> \
+    --enable-app-routing \
+    --enable-addons open-service-mesh \
+    --generate-ssh-keys 
 ```
 
 ### Enable on an existing cluster
@@ -104,7 +115,12 @@ az aks enable-addons --resource-group <ResourceGroupName> --name <ClusterName> -
 To enable application routing on a new cluster, use the [`az aks create`][az-aks-create] command, specifying `--enable-app-routing` flag.
 
 ```azurecli-interactive
-az aks create --resource-group <ResourceGroupName> --name <ClusterName> --location <Location> --enable-app-routing
+az aks create \
+    --resource-group <ResourceGroupName> \
+    --name <ClusterName> \
+    --location <Location> \
+    --enable-app-routing \
+    --generate-ssh-keys
 ```
 
 ### Enable on an existing cluster

articles/aks/auto-upgrade-node-os-image.md

@@ -41,7 +41,11 @@ The following upgrade channels are available. You're allowed to choose one of th
 * Set the node OS auto-upgrade channel on a new cluster using the [`az aks create`][az-aks-create] command with the `--node-os-upgrade-channel` parameter. The following example sets the node OS auto-upgrade channel to `SecurityPatch`.
 
     ```azurecli-interactive
-    az aks create --resource-group myResourceGroup --name myAKSCluster --node-os-upgrade-channel SecurityPatch
+    az aks create \
+        --resource-group myResourceGroup \
+        --name myAKSCluster \
+        --node-os-upgrade-channel SecurityPatch \
+        --generate-ssh-keys
     ```
 
 ### [Azure portal](#tab/azure-portal)

articles/aks/azure-blob-csi.md

@@ -47,7 +47,11 @@ Using the Azure CLI, you can enable the Blob storage CSI driver on a new or exis
 To enable the driver on a new cluster, include the `--enable-blob-driver` parameter with the `az aks create` command as shown in the following example:
 
 ```azurecli
-az aks create --enable-blob-driver --name myAKSCluster --resource-group myResourceGroup
+az aks create \
+    --enable-blob-driver \
+    --name myAKSCluster \
+    --resource-group myResourceGroup \
+    --generate-ssh-keys
 ```
 
 To enable the driver on an existing cluster, include the `--enable-blob-driver` parameter with the `az aks update` command as shown in the following example:

articles/aks/azure-cni-overlay.md

@@ -106,11 +106,14 @@ clusterName="myOverlayCluster"
 resourceGroup="myResourceGroup"
 location="westcentralus"
 
-az aks create -n $clusterName -g $resourceGroup \
-  --location $location \
-  --network-plugin azure \
-  --network-plugin-mode overlay \
-  --pod-cidr 192.168.0.0/16
+az aks create \
+    --name $clusterName \
+    --resource-group $resourceGroup \
+    --location $location \
+    --network-plugin azure \
+    --network-plugin-mode overlay \
+    --pod-cidr 192.168.0.0/16 \
+    --generate-ssh-keys
 ```
 
 ## Add a new nodepool to a dedicated subnet
@@ -239,10 +242,14 @@ 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> \
-      --network-plugin azure \
-      --network-plugin-mode overlay \
-      --ip-families ipv4,ipv6
+    az aks create \
+        --location <region> \
+        --resource-group <resourceGroupName> \
+        --name <clusterName> \
+        --network-plugin azure \
+        --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.