AWS eks documentation change
Summary
Added detailed section about Network Resource Management including prefix delegation, cooldown management, IPv6 support, and network interface management
Security assessment
The changes describe operational aspects of network resource management without addressing specific security vulnerabilities or introducing new security features. Mentions of security groups are part of standard networking configuration.
Diff
diff --git a/eks/latest/userguide/auto-networking.md b/eks/latest/userguide/auto-networking.md index fac6fe836..7bd24ab7e 100644 --- a//eks/latest/userguide/auto-networking.md +++ b//eks/latest/userguide/auto-networking.md @@ -79,0 +80,18 @@ EKS Auto Mode does **not** support: +### Network Resource Management + +EKS Auto Mode handles prefix, IP addressing, and network interface management by monitoring NodeClass resources for networking configurations. The service performs several key operations automatically: + +**Prefix Delegation** + +EKS Auto Mode provisions `/28` IPv4 prefixes to the primary network interface for nodes and maintains a predefined warm pool of resources that scales based on the number of scheduled pods. When necessary, it provisions secondary network interfaces with identical security groups as the primary interface in the node’s subnet. If prefixes are no longer available in the subnet, the service falls back to secondary IPv4 addresses. + +**Cooldown Management** + +The service implements a cooldown pool for prefixes or secondary IPv4 addresses that are no longer in use. After the cooldown period expires, these resources are released back to the VPC. However, if pods reuse these resources during the cooldown period, they are restored from the cooldown pool. + +**IPv6 Support** + +For IPv6 clusters, EKS Auto Mode provisions a `/80` IPv6 prefix per node on the primary network interface. + +The service also ensures proper management and garbage collection of all network interfaces. +