You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/operator-nexus/howto-cluster-runtime-upgrade.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,11 +16,11 @@ This how-to guide explains the steps for installing the required Azure CLI and e
16
16
17
17
## Prerequisites
18
18
19
-
1. The [Install Azure CLI](/cli/azure/install-azure-cli) must be installed.
20
-
2. The `networkcloud` CLI extension is required. If the `networkcloud` extension isn't installed, it can be installed following the steps listed [here](./howto-install-cli-extensions.md).
21
-
3. Access to the Azure portal for the target cluster to be upgraded.
22
-
4. You must be logged in to the same subscription as your target cluster via `az login`
23
-
5. Target cluster must be in a running state, with all control plane nodes healthy and 80+% of compute nodes in a running and healthy state.
19
+
- The [Install Azure CLI](/cli/azure/install-azure-cli) must be installed.
20
+
- The `networkcloud` CLI extension is required. If the `networkcloud` extension isn't installed, it can be installed following the steps listed [here](./howto-install-cli-extensions.md).
21
+
- Access to the Azure portal for the target cluster to be upgraded.
22
+
- You must be logged in to the same subscription as your target cluster via `az login`
23
+
- Target cluster must be in a running state, with all control plane nodes healthy and 80+% of compute nodes in a running and healthy state.
24
24
25
25
## Finding available runtime versions
26
26
@@ -138,7 +138,7 @@ In this example, if less than 10 compute nodes being provisioned in a rack fail
138
138
> ***`update-strategy` cannot be changed after the cluster runtime upgrade has started.***
139
139
> When a threshold value below 100% is set, it’s possible that any unhealthy nodes might not be upgraded, yet the “Cluster” status could still indicate that upgrade was successful. For troubleshooting issues with bare metal machines, please refer to [Troubleshoot Azure Operator Nexus server problems](troubleshoot-reboot-reimage-replace.md)
140
140
141
-
## Upgrading cluster runtime using CLI
141
+
## Upgrade cluster runtime using CLI
142
142
143
143
To perform an upgrade of the runtime, use the following Azure CLI command:
0 commit comments