Skip to content

Documentation: correct version drift limits in cluster-upgrade.md #7994

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

Merged
cPu1 merged 1 commit into from
Oct 17, 2024
Merged

Documentation: correct version drift limits in cluster-upgrade.md #7994

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
8 changes: 4 additions & 4 deletions userdocs/src/usage/cluster-upgrade.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,11 +12,11 @@ An _`eksctl`-managed_ cluster can be upgraded in 3 easy steps:
Please make sure to read this section in full before you proceed.

???+ info
Kubernetes supports version drift of up-to two minor versions during upgrade
process. So nodes can be up to two minor versions ahead or behind the control plane
Kubernetes supports version drift of up to two minor versions during the upgrade
process. Nodes can be up to two minor versions behind, but never ahead of the control plane
version. You can only upgrade the control plane one minor version at a time, but
nodes can be upgraded more than one minor version at a time, provided the nodes stay
within two minor versions of the control plane.
nodes can be upgraded more than one minor version at a time, provided their version
does not become greater than the control plane version.

???+ info
The old `eksctl update cluster` will be deprecated. Use `eksctl upgrade cluster` instead.
Expand Down