Skip to content

Commit 74bdc2c

Browse files
authored
Update howto-cluster-runtime-upgrade.md
1 parent 3b7dad2 commit 74bdc2c

File tree

1 file changed

+12
-12
lines changed

1 file changed

+12
-12
lines changed

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

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ Available upgrades are retrievable via the Azure CLI:
4848
```azurecli
4949
az networkcloud cluster show --name "<CLUSTER>" \
5050
--resource-group "<CLUSTER_RG>" \
51-
--subscription <SUBSCRIPTION> | grep -A8 availableUpgradeVersions
51+
--subscription "<SUBSCRIPTION>" | grep -A8 availableUpgradeVersions
5252
```
5353

5454
In the output, you can find the `availableUpgradeVersions` property and look at the `targetClusterVersion` field:
@@ -73,12 +73,12 @@ If there are no available cluster upgrades, the list is empty.
7373
The following Azure CLI command is used to configure the compute threshold parameters for a runtime upgrade:
7474

7575
```azurecli
76-
az networkcloud cluster update --name "<CLUSTER>" /
76+
az networkcloud cluster update --name "<CLUSTER>" \
7777
--resource-group "<CLUSTER_RG>" \
78-
--update-strategy strategy-type="<strategyType>" threshold-type="<thresholdType" \
79-
threshold-value="<thresholdValue>" max-unavailable=<maxNodesOffline> \
80-
wait-time-minutes=<waitTimeBetweenRacks> \
81-
--subscription <SUBSCRIPTION>
78+
--update-strategy strategy-type="<strategyType>" threshold-type="<thresholdType>" \
79+
threshold-value="<thresholdValue>" max-unavailable="<maxNodesOffline>" \
80+
wait-time-minutes="<waitTimeBetweenRacks>" \
81+
--subscription "<SUBSCRIPTION>"
8282
```
8383

8484
Required parameters:
@@ -97,15 +97,15 @@ az networkcloud cluster update --name "<CLUSTER>" \
9797
--resource-group "<CLUSTER_RG>" \
9898
--update-strategy strategy-type="Rack" threshold-type="PercentSuccess" \
9999
threshold-value=60 wait-time-minutes=1 \
100-
--subscription <SUBSCRIPTION>
100+
--subscription "<SUBSCRIPTION>"
101101
```
102102

103103
Verify update:
104104

105105
```
106106
az networkcloud cluster show --name "<CLUSTER>" \
107107
--resource-group "<CLUSTER_RG>" \
108-
--subscription <SUBSCRIPTION> | grep -A5 updateStrategy
108+
--subscription "<SUBSCRIPTION>" | grep -A5 updateStrategy
109109
110110
"updateStrategy": {
111111
"maxUnavailable": 32767,
@@ -124,15 +124,15 @@ az networkcloud cluster update --name "<CLUSTER>" \
124124
--resource-group "<CLUSTER_RG>" \
125125
--update-strategy strategy-type="Rack" threshold-type="CountSuccess" \
126126
threshold-value=10 wait-time-minutes=1 \
127-
--subscription <SUBSCRIPTION>
127+
--subscription "<SUBSCRIPTION>"
128128
```
129129

130130
Verify update:
131131

132132
```
133133
az networkcloud cluster show --name "<CLUSTER>" \
134134
--resource-group "<CLUSTER_RG>" \
135-
--subscription <SUBSCRIPTION> | grep -A5 updateStrategy
135+
--subscription "<SUBSCRIPTION>" | grep -A5 updateStrategy
136136
137137
"updateStrategy": {
138138
"maxUnavailable": 32767,
@@ -156,7 +156,7 @@ To perform an upgrade of the runtime, use the following Azure CLI command:
156156
az networkcloud cluster update-version --cluster-name "<CLUSTER>" \
157157
--target-cluster-version "<versionNumber>" \
158158
--resource-group "<CLUSTER_RG>" \
159-
--subscription <SUBSCRIPTION>
159+
--subscription "<SUBSCRIPTION>"
160160
```
161161

162162
The runtime upgrade is a long process. The upgrade first upgrades the management nodes and then sequentially Rack by Rack for the worker nodes.
@@ -180,7 +180,7 @@ To view the upgrade status through the Azure CLI, use `az networkcloud cluster s
180180
```azurecli
181181
az networkcloud cluster show --cluster-name "<CLUSTER>" \
182182
--resource-group "<CLUSTER_RG>" \
183-
--subscription <SUBSCRIPTION>
183+
--subscription "<SUBSCRIPTION>"
184184
```
185185

186186
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)