Skip to content

Commit d866a95

Browse files
committed
update language on how spare node is upgraded
1 parent 75cd754 commit d866a95

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/operator-nexus/concepts-cluster-upgrade-overview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ Patch runtime release is produced monthly in between the minor releases. These r
3434

3535
Starting a runtime upgrade is defined under [Upgrading cluster runtime via Azure CLI](./howto-cluster-runtime-upgrade.md).
3636

37-
The runtime upgrade starts by upgrading the three management servers designated as the control plane nodes. The spare control plane server will remain down during this time. These servers are updated serially and proceed only when each completes. The remaining management servers are upgraded into four different groups and completed one group at a time.
37+
The runtime upgrade starts by upgrading the three management servers designated as the control plane nodes. The spare control plane server is the first server to upgrade. The last control plane server deprovisions and transitions to `Available` state. These servers are updated serially and proceed only when each completes. The remaining management servers are upgraded into four different groups and completed one group at a time.
3838

3939
> [!Note]
4040
> Customers may observe the spare server with a different runtime version. This is expected.
@@ -78,4 +78,4 @@ During the runtime upgrade, BareMetalMachine (BMM) keyset isn't available until
7878

7979
## Servers not upgraded successfully
8080

81-
A server remains cordoned if they fail upgrade or provisioning from possible hardware issue during reboot or issue with cloud-init (networking, chronyd, etc.). The underlying condition needs to be resolved and either bmm replace/reimage would need to be executed. Likely Uncordoning the bmm manually will not resolve.
81+
A server remains cordoned if they fail upgrade or provisioning from possible hardware issue during reboot or issue with cloud-init (networking, chronyd, etc.). The underlying condition needs to be resolved and either baremetalmachine replace/reimage would need to be executed. Uncordoning the server manually won't resolve the issues.

0 commit comments

Comments
 (0)