EKS Node Scaling with Karpenter

Question

Hi everyone,

I'm working with an EKS cluster that has three node groups. When I attempt to scale a deployment to the maximum CPU capacity, the cluster automatically provisions additional nodes. However, these new nodes aren't assigned to any specific node group.

**My question is**: How can I ensure that newly created nodes are added to a particular node group?

**Here's the current behavior:**
Scaling the deployment to the CPU limit triggers cluster autoscaling (potentially using Karpenter).
Karpenter creates new EC2 instances to meet the increasing resource demands.
These new instances are not explicitly associated with any existing node group.

**Desired behavior:**
I want new nodes to be added to a specific node group during cluster autoscaling.

Answer

You can follow these steps  to ensure that a newly created nodes are added to a specific node group during cluster autoscaling with karpenter in EKS

Assign unique labels to your existing node groups. You can do this during the creation of the node groups or by updating the existing ones.

Modify the Karpenter configuration to specify a node group selector. This selector will tell Karpenter which node group to target when provisioning new nodes.

Ensure that the Karpenter configuration includes the node group selector option and specifies the label of the desired node group.

After updating the Karpenter configuration, monitor the cluster autoscaling events and verify that new nodes are being added to the correct node group.

I think it will be more clearer to paste your yaml file here and cover the sensitive info or if you can follow the above steps i think everything should be ok

EKS Node Scaling with Karpenter

Relevant content