Merge remote-tracking branch 'github/mainline' into mainline

Author: pgasca

latest/ug/automode/auto-change.adoc

@@ -14,10 +14,20 @@ To receive notifications of all source file changes to this specific documentati
 https://github.com/awsdocs/amazon-eks-user-guide/commits/mainline/latest/ug/automode/auto-change.adoc.atom
 ----
 
+== September 30, 2025
+
+*Feature:* Added support for instanceProfile to the NodeClass `spec.instanceProfile` which is mutually exclusive from the `spec.role` field.
+
+== September 29, 2025
+
+DRA is not currently supported by EKS Auto Mode.
+
+
 == September 10, 2025
 
 *Chore:* Events fired from the Auto Mode Compute controller will now use the name `eks-auto-mode/compute` instead of `karpenter`.
 
+
 == August 24, 2025
 
 *Bug Fix:* VPCs that used a DHCP option set with a custom domain name that contained capital letters would cause Nodes to fail to join the cluster due to generating an invalid hostname. This has been resolved and domain names with capital letters now work correctly.

latest/ug/automode/auto-networking.adoc

@@ -46,7 +46,6 @@ EKS Auto Mode does *not* support:
 * Custom Networking in the `ENIConfig`. You can put pods in multiple subnets or exclusively isolate them from the node traffic with <<pod-subnet-selector>>.
 * Warm IP, warm prefix, and warm ENI configurations.
 * Minimum IP targets configuration.
-* Enabling or disabling prefix delegation.
 * Other configurations supported by the open source {aws} VPC CNI.
 * Network Policy configurations such as conntrack timer customization (default is 300s).
 * Exporting network event logs to CloudWatch.
@@ -57,7 +56,9 @@ EKS Auto Mode handles prefix, IP addressing, and network interface management by
 
 *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.
+EKS Auto Mode defaults to using prefix delegation (/28 prefixes) for pod networking and maintains a predefined warm pool of IP resources that scales based on the number of scheduled pods. When pod subnet fragmentation is detected, Auto Mode provisions secondary IP addresses (/32). Due to this default pod networking algorithm, Auto Mode calculates max pods per node based on the number of ENIs and IPs supported per instance type (assuming the worst case of fragmentation). For more information about Max ENIs and IPs per instance type, see link:AWSEC2/latest/UserGuide/AvailableIpPerENI.html[Maximum IP addresses per network interface,type="documentation"] in the EC2 User Guide. Newer generation (Nitro v6 and above) instance families generally have increased ENIs and IPs per instance type, and Auto Mode adjusts the max pods calculation accordingly.
+
+For IPv6 clusters, only prefix delegation is used, and Auto Mode always uses a max pods limit of 110 pods per node.
 
 *Cooldown Management*
 

latest/ug/automode/create-node-class.adoc

@@ -117,7 +117,12 @@ metadata:
   name: my-node-class
 spec:
   # Required fields
+
+  # role and instanceProfile are mutually exclusive fields.
   role: MyNodeRole  # IAM role for EC2 instances
+  # NOTE: instance profile names must start with the 'eks' prefix. this is a
+  # temporary limitation to be lifted soon.
+  # instanceProfile: eks-MyNodeInstanceProfile  # IAM instance-profile for EC2 instances
   
   subnetSelectorTerms:
     - tags: