AWS eks documentation change
Summary
Updated Kubernetes version references from 1.33 to 1.35 in eksctl commands and changed example node version from 1.31 to 1.33 in tainting/draining instructions.
Security assessment
Version number updates reflect current Kubernetes releases without referencing security fixes, vulnerabilities, or incidents. The changes maintain version compatibility guidance but contain no security-specific content or evidence of addressing security issues.
Diff
diff --git a/eks/latest/userguide/migrate-stack.md b/eks/latest/userguide/migrate-stack.md index 6ced64b96..b912013ef 100644 --- a//eks/latest/userguide/migrate-stack.md +++ b//eks/latest/userguide/migrate-stack.md @@ -66 +66 @@ For more available flags and their descriptions, see https://eksctl.io/. - --version 1.33 \ + --version 1.35 \ @@ -158 +158 @@ Replace the `ARN of instance role (not instance profile)` snippet with the **Nod -If you’re upgrading your nodes to a new Kubernetes version, you can identify and taint all of the nodes of a particular Kubernetes version (in this case, `1.31`) with the following code snippet. The version number can’t be later than the Kubernetes version of your control plane. It also can’t be more than two minor versions earlier than the Kubernetes version of your control plane. We recommend that you use the same version as your control plane. +If you’re upgrading your nodes to a new Kubernetes version, you can identify and taint all of the nodes of a particular Kubernetes version (in this case, `1.33`) with the following code snippet. The version number can’t be later than the Kubernetes version of your control plane. It also can’t be more than two minor versions earlier than the Kubernetes version of your control plane. We recommend that you use the same version as your control plane. @@ -160 +160 @@ If you’re upgrading your nodes to a new Kubernetes version, you can identify a - K8S_VERSION=1.31 + K8S_VERSION=1.33 @@ -185 +185 @@ An example output is as follows. This cluster is using CoreDNS for DNS resolutio -If you’re upgrading your nodes to a new Kubernetes version, identify and drain all of the nodes of a particular Kubernetes version (in this case, `1.31`) with the following code snippet. +If you’re upgrading your nodes to a new Kubernetes version, identify and drain all of the nodes of a particular Kubernetes version (in this case, `1.33`) with the following code snippet. @@ -187 +187 @@ If you’re upgrading your nodes to a new Kubernetes version, identify and drain - K8S_VERSION=1.31 + K8S_VERSION=1.33