Skip to content

Enhance cluster upgrade overview with detailed process #4300

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
deepukraju wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Enhance cluster upgrade overview with detailed process #4300

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions operator-nexus/concepts-cluster-upgrade-overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,6 +43,7 @@ The runtime upgrade starts by upgrading the three management servers designated

> [!Note]
> Customers may observe the spare server with a different runtime version. This is expected.
> If the EnableRepurposeSpareKcpNode feature is enabled, a healthy management plane node is first promoted to a spare control plane node before the control plane upgrade begins. After all control plane nodes are upgraded, the spare control plane node is converted back to a management plane node.

Once all management servers are upgraded, the upgrade progresses to the compute servers. Each rack is upgraded in alphanumeric order, and there are various configurations customers can use to dictate how the computes are upgrade to best limit disruption. As each rack progresses, there are various health checks performed in order to ensure the release successfully upgrades and a sufficient number of computes in a rack returns to operational status. When a rack completes, a customer defined waits time starts to provide extra time for workloads to come online. Once each rack upgrades, the upgrade completes and the cluster returns to `Running` status.

Expand Down