-
Notifications
You must be signed in to change notification settings - Fork 978
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
Question: How to limit the max size of a cluster? #1104
Comments
Hi, |
You can specify max resources |
Just a thought here. Just like you have maxPods in addition to cpu/mem, it does make sense to have max nodes. From control plane perspective, each node does have some overhead. That's why it is quite common for e.g CNIs to specify scaling thresholds both in terms of number of pods in the cluster and number of nodes. Granted, some of this should be mitigated by disallowing nodes that are too small, it is still not that unreasonable. Somewhat related to the defrag problem in #1091, karpenter could consider growing the instance sizes when the "maxNodes" limit is approaching. |
@adefrasne @ellistarn thanks, this is what I'm looking for. I want to avoid that an infinite number of nodes are provisioned. We use karpenter to deploy preview environments. |
Hi, how can I ensure the maximum number of nodes? Will
karpenter
respect the configuration of a managed eks cluster (eskctlmaxSize
)?The text was updated successfully, but these errors were encountered: