aws / aws/containers-roadmap

Node Pools not able to use t3.small in AWS EKS Auto Mode

Open
#2,516 4 comments 0 reactions 0 assignees View on GitHub
EKS EKS Auto Mode Proposed
Dominant language
Shell
Stars
5.4k
Forks
334
PR merge metrics
No merged PRs in 30d

Description

We have facing issue while creating custom nodepool with t3.small in AWS EKS Auto Mode.

Working with t3.medium instance type however facing issue only with t3.small. We have also adjusted the CPU and Memory limits and requests for your daemon set and tried still it is picking up the t3.medium size.

Upon checking the nodeclaim that was created by EKS automode Karpenter while creating the node I have seen below config which does not contain small instance size could be the one of the possible reasons it is not picking up the small sized instances as Automode always make sures that enough resources are always available.

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the reported EKS Auto Mode nodeclaim configuration and compare the available instance sizes with the requested t3.small and working t3.medium cases. Check how the daemonset CPU and memory requests affect the selected size, then confirm the expected behavior for custom nodepools in AWS EKS Auto Mode.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, kubernetes
Domain
cloud, devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.