From 5bf17fd2cbd012bcbc783167f994663f4e4ce705 Mon Sep 17 00:00:00 2001 From: Martin Harriman Date: Tue, 8 Oct 2024 21:46:51 +0000 Subject: [PATCH] Correct version drift in cluster-upgrade.md Correct the description of version drift during upgrade to match the current kubernetes documentation. Node version should not be newer than the cluster version. --- userdocs/src/usage/cluster-upgrade.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/userdocs/src/usage/cluster-upgrade.md b/userdocs/src/usage/cluster-upgrade.md index 26dd490eb1a..4b05b876ce4 100644 --- a/userdocs/src/usage/cluster-upgrade.md +++ b/userdocs/src/usage/cluster-upgrade.md @@ -12,8 +12,8 @@ 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 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.