@@ -39,7 +39,9 @@ From the **available upgrade versions** tab, we're able to see the different clu
39
39
Available upgrades are retrievable via the Azure CLI:
40
40
41
41
``` 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>
43
45
```
44
46
45
47
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
141
143
To perform an upgrade of the runtime, use the following Azure CLI command:
142
144
143
145
``` 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>
146
150
```
147
151
148
152
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
164
168
To view the upgrade status through the Azure CLI, use ` az networkcloud cluster show ` .
165
169
166
170
``` 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>
168
174
```
169
175
170
176
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