Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Karpenter picks large instances #196

Open
asmacdo opened this issue Sep 9, 2024 · 0 comments
Open

Karpenter picks large instances #196

asmacdo opened this issue Sep 9, 2024 · 0 comments

Comments

@asmacdo
Copy link
Member

asmacdo commented Sep 9, 2024

In our default NodePool (everything but on-demand and GPU) Karpenter has the following matrix of options:

instanceSizes: ["xlarge", "2xlarge", "4xlarge", "8xlarge", "16xlarge", "24xlarge"]                                          
instanceFamilies: ["c5", "m5", "r5"]  

However, there are cases where a very large/expensive node gets deployed to accommodate potentially many user-pods, but are kept live for just 1 user.

For example, a user has been running a "Base" profile instance, but it has been running on an r5.24xlarge. I'm not sure what conditions led to this, but the user has been alone on this expensive node for some time.

IMO we should force Karpenter to pick smaller nodes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant