Skip to content

Commit 071d50c

Browse files
committed
Updated ssh doc
1 parent ed363bb commit 071d50c

File tree

1 file changed

+13
-11
lines changed

1 file changed

+13
-11
lines changed

articles/operator-nexus/howto-kubernetes-cluster-manage-ssh-key.md

Lines changed: 13 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -92,10 +92,10 @@ Update the quickstart ARM template or Bicep parameter file with the required key
9292
"controlPlaneSshKeys": {
9393
"value": [
9494
{
95-
"keyData": "ssh-rsa AAAAA...."
95+
"keyData": "ssh-rsa CCCCC...."
9696
},
9797
{
98-
"keyData": "ssh-rsa BBBBB...."
98+
"keyData": "ssh-rsa DDDDD...."
9999
}
100100
]
101101
}
@@ -107,15 +107,17 @@ Update the quickstart ARM template or Bicep parameter file with the required key
107107
"agentPoolSshKeys": {
108108
"value": [
109109
{
110-
"keyData": "ssh-rsa AAAAA...."
110+
"keyData": "ssh-rsa EEEEE...."
111111
},
112112
{
113-
"keyData": "ssh-rsa BBBBB...."
113+
"keyData": "ssh-rsa FFFFF...."
114114
}
115115
]
116116
}
117117
```
118118

119+
Apply the ARM template or Bicep to create the cluster.
120+
119121
---
120122

121123
## Manage Operator Nexus Kubernetes cluster node SSH keys
@@ -126,7 +128,7 @@ To update the SSH keys, you can apply the same Bicep/ARM configuration used duri
126128

127129
### Limitations
128130

129-
1. You can't remove all SSH keys from the cluster nodes. You can only update them with new keys.
131+
1. You can't remove SSH keys from the cluster nodes. You can only update them with new keys.
130132
2. If you try to update the cluster wide key with an empty array, the operation succeeds, but the existing keys remain unchanged.
131133
3. If you try to update the agent pool keys or control plane with an empty array, the operation succeeds, and the cluster wide keys are used instead.
132134
4. If you try to update the keys for a cluster that was created without any keys, the new key is added, but you can't remove it.
@@ -147,16 +149,16 @@ Use the following command to update the cluster wide SSH keys, which are used fo
147149
148150
#### Azure CLI to update cluster wide SSH keys
149151

150-
1. Set the `NEW_CLUSTER_WIDE_KEY` variable with the new SSH key.
152+
1. Set the `SSH_PUBLIC_KEY` variable with the new SSH key.
151153

152154
```bash
153-
NEW_CLUSTER_WIDE_KEY="ssh-rsa CCCCC...."
155+
SSH_PUBLIC_KEY="ssh-rsa CCCCC...."
154156
```
155157

156158
2. Use the following command to update the cluster wide SSH keys.
157159

158160
```azurecli
159-
az networkcloud kubernetescluster update --name "$CLUSTER_NAME" --resource-group "$RESOURCE_GROUP" --subscription "$SUBSCRIPTION_ID" --ssh-key-values "$CLUSER_WIDE_KEY"
161+
az networkcloud kubernetescluster update --name "$CLUSTER_NAME" --resource-group "$RESOURCE_GROUP" --subscription "$SUBSCRIPTION_ID" --ssh-key-values "$SSH_PUBLIC_KEY"
160162
```
161163

162164
#### Azure Resource Manager (ARM) and Bicep to update cluster wide SSH keys
@@ -259,16 +261,16 @@ Use the following command to update the SSH keys for the control plane.
259261
260262
#### Azure CLI to update control plane SSH keys
261263

262-
1. Set the `CONTROL_PLANE_KEY` variable with the new SSH key.
264+
1. Set the `CONTROL_PLANE_SSH_PUBLIC_KEY` variable with the new SSH key.
263265

264266
```bash
265-
CONTROL_PLANE_KEY="ssh-rsa EEEEE...."
267+
CONTROL_PLANE_SSH_PUBLIC_KEY="ssh-rsa EEEEE...."
266268
```
267269

268270
2. Use the following command to update the control plane SSH keys.
269271

270272
```azurecli
271-
az networkcloud kubernetescluster update --name "$CLUSTER_NAME" --resource-group "$RESOURCE_GROUP" --subscription "$SUBSCRIPTION_ID" --control-plane-node-configuration ssh-key-values="['$CONTROL_PLANE_KEY']"
273+
az networkcloud kubernetescluster update --name "$CLUSTER_NAME" --resource-group "$RESOURCE_GROUP" --subscription "$SUBSCRIPTION_ID" --control-plane-node-configuration ssh-key-values="['$CONTROL_PLANE_SSH_PUBLIC_KEY']"
272274
```
273275

274276
#### Azure ARM template and Bicep to update control plane SSH keys

0 commit comments

Comments
 (0)