AWS Security ChangesHomeSearch

AWS eks documentation change

Service: eks · 2025-06-25 · Documentation low

File: eks/latest/userguide/migrate-stack.md

Summary

Updated Kubernetes version references from 1.30 to 1.31 in node upgrade examples and documentation

Security assessment

The changes update example Kubernetes versions for node upgrade procedures. While the text mentions version compatibility requirements, there is no explicit reference to security fixes or vulnerabilities being addressed by these version changes.

Diff

diff --git a/eks/latest/userguide/migrate-stack.md b/eks/latest/userguide/migrate-stack.md
index cdc0f0b59..131884eab 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/](https:
-      --version 1.32 \
+      --version 1.33 \
@@ -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.30`) 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.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.
@@ -160 +160 @@ If you’re upgrading your nodes to a new Kubernetes version, you can identify a
-        K8S_VERSION=1.30
+        K8S_VERSION=1.31
@@ -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.30`) 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.31`) with the following code snippet.
@@ -187 +187 @@ If you’re upgrading your nodes to a new Kubernetes version, identify and drain
-        K8S_VERSION=1.30
+        K8S_VERSION=1.31