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

Cluster Autoscaler error in EKS node group comparison of missing capacity #7513

Open
chriswvu opened this issue Nov 21, 2024 · 0 comments
Open
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@chriswvu
Copy link

Which component are you using?:

cluster-autoscaler

What version of the component are you using?:

Component version: 1.30

What k8s version are you using (kubectl version)?: 1.30

kubectl version Output
$ kubectl version

What environment is this in?: AWS / EKS

What did you expect to happen?:

With the --balance-similar-node-groups flag expected that nodes would be added balanced across multiple node groups.

The node groups are configured with the exact same instance type. t3.medium

What happened instead?:

Node were created in a single node group. Getting errors in the logs of missing capacity like:

compare_nodegroups.go:126] nodes template-node-for-eks-6008110688907257595 and template-node-for-eks-1601417514495495517 are not similar, missing capacity hugepages-1Gi
compare_nodegroups.go:126] nodes template-node-for-eks-6008110688907257595 and template-node-for-eks-4358223196786636438 are not similar, missing capacity ephemeral-storage
compare_nodegroups.go:132] nodes template-node-for-eks-1601417514495495517 and template-node-for-eks-6008110688907257595 are not similar, memory not within tolerance

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

@chriswvu chriswvu added the kind/bug Categorizes issue or PR as related to a bug. label Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

1 participant