Skip to content

Commit 4726987

Browse files
authored
Update howto-cluster-runtime-upgrade.md
1 parent 8603acc commit 4726987

File tree

1 file changed

+10
-4
lines changed

1 file changed

+10
-4
lines changed

articles/operator-nexus/howto-cluster-runtime-upgrade.md

Lines changed: 10 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,9 @@ From the **available upgrade versions** tab, we're able to see the different clu
3939
Available upgrades are retrievable via the Azure CLI:
4040

4141
```azurecli
42-
az networkcloud cluster show --name "clusterName" --resource-group "resourceGroup"
42+
az networkcloud cluster show --name "<clusterName>" /
43+
--resource-group "<resourceGroup>" /
44+
--subscription <SUBSCRIPTION_ID>
4345
```
4446

4547
In the output, you can find the `availableUpgradeVersions` property and look at the `targetClusterVersion` field:
@@ -141,8 +143,10 @@ In this example, if less than 10 compute nodes being provisioned in a rack fail
141143
To perform an upgrade of the runtime, use the following Azure CLI command:
142144

143145
```azurecli
144-
az networkcloud cluster update-version --cluster-name "clusterName" --target-cluster-version
145-
"versionNumber" --resource-group "resourceGroupName"
146+
az networkcloud cluster update-version --cluster-name "<clusterName>" /
147+
--target-cluster-version "<versionNumber>" /
148+
--resource-group "<resourceGroupName>" /
149+
--subscription <SUBSCRIPTION_ID>
146150
```
147151

148152
The runtime upgrade is a long process. The upgrade first upgrades the management nodes and then sequentially rack by rack for the worker nodes.
@@ -164,7 +168,9 @@ The Cluster upgrade is complete when detailedStatus is set to `Running` and deta
164168
To view the upgrade status through the Azure CLI, use `az networkcloud cluster show`.
165169

166170
```azurecli
167-
az networkcloud cluster show --cluster-name "clusterName" --resource-group "resourceGroupName"
171+
az networkcloud cluster show --cluster-name "<clusterName>" /
172+
--resource-group "<resourceGroupName>" /
173+
--subscription <SUBSCRIPTION_ID>
168174
```
169175

170176
The output should be the target cluster's information and the cluster's detailed status and detail status message should be present.

0 commit comments

Comments
 (0)