Amazon Elastic Kubernetes Service Update: EKS MNG WarmPool feature to support ASG WarmPool feature.

Author: AWS

.changes/next-release/feature-AmazonElasticKubernetesService-fdd8e87.json

@@ -0,0 +1,6 @@
+{
+    "type": "feature",
+    "category": "Amazon Elastic Kubernetes Service",
+    "contributor": "",
+    "description": "EKS MNG WarmPool feature to support ASG WarmPool feature."
+}

services/eks/src/main/resources/codegen-resources/service-2.json

@@ -2932,6 +2932,10 @@
         "releaseVersion":{
           "shape":"String",
           "documentation":"<p>The AMI version of the Amazon EKS optimized AMI to use with your node group. By default, the latest available AMI version for the node group's current Kubernetes version is used. For information about Linux versions, see <a href=\"https://docs.aws.amazon.com/eks/latest/userguide/eks-linux-ami-versions.html\">Amazon EKS optimized Amazon Linux AMI versions</a> in the <i>Amazon EKS User Guide</i>. Amazon EKS managed node groups support the November 2022 and later releases of the Windows AMIs. For information about Windows versions, see <a href=\"https://docs.aws.amazon.com/eks/latest/userguide/eks-ami-versions-windows.html\">Amazon EKS optimized Windows AMI versions</a> in the <i>Amazon EKS User Guide</i>.</p> <p>If you specify <code>launchTemplate</code>, and your launch template uses a custom AMI, then don't specify <code>releaseVersion</code>, or the node group deployment will fail. For more information about using launch templates with Amazon EKS, see <a href=\"https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html\">Customizing managed nodes with launch templates</a> in the <i>Amazon EKS User Guide</i>.</p>"
+        },
+        "warmPoolConfig":{
+          "shape":"WarmPoolConfig",
+          "documentation":"<p>The warm pool configuration for the node group. Warm pools maintain pre-initialized EC2 instances that can quickly join your cluster during scale-out events, improving application scaling performance and reducing costs.</p>"
         }
       }
     },
@@ -5417,6 +5421,10 @@
         "tags":{
           "shape":"TagMap",
           "documentation":"<p>Metadata that assists with categorization and organization. Each tag consists of a key and an optional value. You define both. Tags don't propagate to any other cluster or Amazon Web Services resources.</p>"
+        },
+        "warmPoolConfig":{
+          "shape":"WarmPoolConfig",
+          "documentation":"<p>The warm pool configuration attached to the node group. Amazon EKS manages warm pools throughout the node group lifecycle using the <code>AWSServiceRoleForAmazonEKSNodegroup</code> service-linked role to create, update, and delete warm pool resources.</p>"
         }
       },
       "documentation":"<p>An object representing an Amazon EKS managed node group.</p>"
@@ -6697,6 +6705,10 @@
           "shape":"NodeRepairConfig",
           "documentation":"<p>The node auto repair configuration for the node group.</p>"
         },
+        "warmPoolConfig":{
+          "shape":"WarmPoolConfig",
+          "documentation":"<p>The warm pool configuration to apply to the node group. You can use this to add a warm pool to an existing node group or modify the settings of an existing warm pool.</p>"
+        },
         "clientRequestToken":{
           "shape":"String",
           "documentation":"<p>A unique, case-sensitive identifier that you provide to ensure the idempotency of the request.</p>",
@@ -6814,7 +6826,12 @@
         "DeletionProtection",
         "NodeRepairConfig",
         "UpdatedTier",
-        "PreviousTier"
+        "PreviousTier",
+        "WarmPoolEnabled",
+        "WarmPoolMaxGroupPreparedCapacity",
+        "WarmPoolMinSize",
+        "WarmPoolState",
+        "WarmPoolReuseOnScaleIn"
       ]
     },
     "UpdateParams":{
@@ -7019,6 +7036,40 @@
       },
       "documentation":"<p>An object representing an Amazon EKS cluster VPC configuration response.</p>"
     },
+    "WarmPoolConfig":{
+      "type":"structure",
+      "members":{
+        "enabled":{
+          "shape":"BoxedBoolean",
+          "documentation":"<p>Specifies whether to attach warm pools on the managed node group. Set to <code>true</code> to enable the warm pool, or <code>false</code> to disable and remove it. If not specified during an update, the current value is preserved.</p>"
+        },
+        "minSize":{
+          "shape":"ZeroCapacity",
+          "documentation":"<p>The minimum number of instances to maintain in the warm pool. Default: <code>0</code>. Size your warm pool based on scaling patterns to balance cost and availability. Start with 10-20% of expected peak capacity.</p>"
+        },
+        "maxGroupPreparedCapacity":{
+          "shape":"BoxedInteger",
+          "documentation":"<p>The maximum total number of instances across the warm pool and Auto Scaling group combined. This value controls the total prepared capacity available for your node group.</p>"
+        },
+        "poolState":{
+          "shape":"WarmPoolState",
+          "documentation":"<p>The desired state for warm pool instances. Default: <code>Stopped</code>. Valid values are <code>Stopped</code> (most cost-effective with EBS storage costs only), <code>Running</code> (fastest transition time with full EC2 costs), and <code>Hibernated</code> (balance between cost and speed, only supported on specific instance types). Warm pool instances in the <code>Hibernated</code> state are not supported with Bottlerocket AMIs.</p>"
+        },
+        "reuseOnScaleIn":{
+          "shape":"BoxedBoolean",
+          "documentation":"<p>Indicates whether instances should return to the warm pool during scale-in events instead of being terminated. Default: <code>false</code>. Enable this to reduce costs by reusing instances. This feature is not supported for Bottlerocket AMIs.</p>"
+        }
+      },
+      "documentation":"<p>The configuration for an Amazon EC2 Auto Scaling warm pool attached to an Amazon EKS managed node group. Warm pools maintain pre-initialized EC2 instances alongside your Auto Scaling group that have already completed the bootup initialization process and can be kept in a <code>Stopped</code>, <code>Running</code>, or <code>Hibernated</code> state.</p>"
+    },
+    "WarmPoolState":{
+      "type":"string",
+      "enum":[
+        "STOPPED",
+        "RUNNING",
+        "HIBERNATED"
+      ]
+    },
     "ZeroCapacity":{
       "type":"integer",
       "box":true,