Skip to content

Commit d6d276c

Browse files
committed
add --generate-ssh-keys to az aks create calls
1 parent f433b9e commit d6d276c

File tree

7 files changed

+71
-34
lines changed

7 files changed

+71
-34
lines changed

articles/aks/ai-toolchain-operator.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -96,7 +96,8 @@ The following sections describe how to create an AKS cluster with the AI toolcha
9696
--resource-group ${AZURE_RESOURCE_GROUP} \
9797
--name ${CLUSTER_NAME} \
9898
--enable-oidc-issuer \
99-
--enable-ai-toolchain-operator
99+
--enable-ai-toolchain-operator \
100+
--generate-ssh-keys
100101
```
101102
102103
> [!NOTE]

articles/aks/aks-migration.md

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -72,14 +72,15 @@ The following example creates an AKS cluster with single node pool backed by a v
7272
7373
```azurecli-interactive
7474
az aks create \
75-
--resource-group myResourceGroup \
76-
--name myAKSCluster \
77-
--node-count 1 \
78-
--vm-set-type VirtualMachineScaleSets \
79-
--load-balancer-sku standard \
80-
--enable-cluster-autoscaler \
81-
--min-count 1 \
82-
--max-count 3
75+
--resource-group myResourceGroup \
76+
--name myAKSCluster \
77+
--node-count 1 \
78+
--vm-set-type VirtualMachineScaleSets \
79+
--load-balancer-sku standard \
80+
--enable-cluster-autoscaler \
81+
--min-count 1 \
82+
--max-count 3 \
83+
--generate-ssh-keys
8384
```
8485
8586
## Existing attached Azure Services

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

Lines changed: 14 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -87,7 +87,8 @@ You can configure your AKS clusters with API Server VNet Integration in managed
8787
--resource-group <resource-group> \
8888
--location <location> \
8989
--network-plugin azure \
90-
--enable-apiserver-vnet-integration
90+
--enable-apiserver-vnet-integration \
91+
--generate-ssh-keys
9192
```
9293
9394
### Deploy a private cluster
@@ -100,7 +101,8 @@ You can configure your AKS clusters with API Server VNet Integration in managed
100101
--location <location> \
101102
--network-plugin azure \
102103
--enable-private-cluster \
103-
--enable-apiserver-vnet-integration
104+
--enable-apiserver-vnet-integration \
105+
--generate-ssh-keys
104106
```
105107
106108
## 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>
180182
181183
```azurecli-interactive
182184
az aks create --name <cluster-name> \
183-
--resource-group <resource-group> \
184-
--location <location> \
185-
--network-plugin azure \
186-
--enable-apiserver-vnet-integration \
187-
--vnet-subnet-id <cluster-subnet-resource-id> \
188-
--apiserver-subnet-id <apiserver-subnet-resource-id> \
189-
--assign-identity <managed-identity-resource-id>
185+
--resource-group <resource-group> \
186+
--location <location> \
187+
--network-plugin azure \
188+
--enable-apiserver-vnet-integration \
189+
--vnet-subnet-id <cluster-subnet-resource-id> \
190+
--apiserver-subnet-id <apiserver-subnet-resource-id> \
191+
--assign-identity <managed-identity-resource-id> \
192+
--generate-ssh-keys
190193
```
191194
192195
### Deploy a private cluster
@@ -202,7 +205,8 @@ az group create --location <location> --name <resource-group>
202205
--enable-apiserver-vnet-integration \
203206
--vnet-subnet-id <cluster-subnet-resource-id> \
204207
--apiserver-subnet-id <apiserver-subnet-resource-id> \
205-
--assign-identity <managed-identity-resource-id>
208+
--assign-identity <managed-identity-resource-id> \
209+
--generate-ssh-keys
206210
```
207211
208212
## Convert an existing AKS cluster to API Server VNet Integration

articles/aks/app-routing.md

Lines changed: 19 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,12 @@ With the retirement of [Open Service Mesh][open-service-mesh-docs] (OSM) by the
5454
To enable application routing on a new cluster, use the [`az aks create`][az-aks-create] command, specifying the `--enable-app-routing` flag.
5555

5656
```azurecli-interactive
57-
az aks create --resource-group <ResourceGroupName> --name <ClusterName> --location <Location> --enable-app-routing
57+
az aks create \
58+
--resource-group <ResourceGroupName> \
59+
--name <ClusterName> \
60+
--location <Location> \
61+
--enable-app-routing \
62+
--generate-ssh-keys
5863
```
5964

6065
### Enable on an existing cluster
@@ -79,7 +84,13 @@ The following add-ons are required to support this configuration:
7984
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:
8085

8186
```azurecli-interactive
82-
az aks create --resource-group <ResourceGroupName> --name <ClusterName> --location <Location> --enable-app-routing --enable-addons open-service-mesh
87+
az aks create \
88+
--resource-group <ResourceGroupName> \
89+
--name <ClusterName> \
90+
--location <Location> \
91+
--enable-app-routing \
92+
--enable-addons open-service-mesh \
93+
--generate-ssh-keys
8394
```
8495

8596
### Enable on an existing cluster
@@ -104,7 +115,12 @@ az aks enable-addons --resource-group <ResourceGroupName> --name <ClusterName> -
104115
To enable application routing on a new cluster, use the [`az aks create`][az-aks-create] command, specifying `--enable-app-routing` flag.
105116

106117
```azurecli-interactive
107-
az aks create --resource-group <ResourceGroupName> --name <ClusterName> --location <Location> --enable-app-routing
118+
az aks create \
119+
--resource-group <ResourceGroupName> \
120+
--name <ClusterName> \
121+
--location <Location> \
122+
--enable-app-routing \
123+
--generate-ssh-keys
108124
```
109125

110126
### Enable on an existing cluster

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

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,11 @@ The following upgrade channels are available. You're allowed to choose one of th
4141
* 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`.
4242

4343
```azurecli-interactive
44-
az aks create --resource-group myResourceGroup --name myAKSCluster --node-os-upgrade-channel SecurityPatch
44+
az aks create \
45+
--resource-group myResourceGroup \
46+
--name myAKSCluster \
47+
--node-os-upgrade-channel SecurityPatch \
48+
--generate-ssh-keys
4549
```
4650
4751
### [Azure portal](#tab/azure-portal)

articles/aks/azure-blob-csi.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,11 @@ Using the Azure CLI, you can enable the Blob storage CSI driver on a new or exis
4747
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:
4848

4949
```azurecli
50-
az aks create --enable-blob-driver --name myAKSCluster --resource-group myResourceGroup
50+
az aks create \
51+
--enable-blob-driver \
52+
--name myAKSCluster \
53+
--resource-group myResourceGroup \
54+
--generate-ssh-keys
5155
```
5256

5357
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

Lines changed: 17 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -106,11 +106,14 @@ clusterName="myOverlayCluster"
106106
resourceGroup="myResourceGroup"
107107
location="westcentralus"
108108
109-
az aks create -n $clusterName -g $resourceGroup \
110-
--location $location \
111-
--network-plugin azure \
112-
--network-plugin-mode overlay \
113-
--pod-cidr 192.168.0.0/16
109+
az aks create \
110+
--name $clusterName \
111+
--resource-group $resourceGroup \
112+
--location $location \
113+
--network-plugin azure \
114+
--network-plugin-mode overlay \
115+
--pod-cidr 192.168.0.0/16 \
116+
--generate-ssh-keys
114117
```
115118

116119
## Add a new nodepool to a dedicated subnet
@@ -239,11 +242,15 @@ The following attributes are provided to support dual-stack clusters:
239242
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`.
240243
241244
```azurecli-interactive
242-
az aks create --location <region> --resource-group <resourceGroupName> --name <clusterName> \
243-
--network-plugin azure \
244-
--network-plugin-mode overlay \
245-
--ip-families ipv4,ipv6
246-
```
245+
az aks create \
246+
--location <region> \
247+
--resource-group <resourceGroupName> \
248+
--name <clusterName> \
249+
--network-plugin azure \
250+
--network-plugin-mode overlay \
251+
--ip-families ipv4,ipv6 \
252+
--generate-ssh-keys
253+
```
247254
248255
---
249256

0 commit comments

Comments
 (0)