-
Notifications
You must be signed in to change notification settings - Fork 136
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
Document the way the Kubernetes scheduler mode impacts Karpenter #1228
Comments
CC @jonathan-innis (this is what I spoke to you at KubeCon EU about) |
Agreed. This sounds like a good feature to explore. Obviously, for us to give a recommendation for those that have direct control of their SchedulerConfiguration and the control plane, but also platforms like EKS should explore this alternative option to see if they get increased performance with Karpenter from this other setting. I suspect that you are right about the performance, at least that we would be able to act more aggressively with consolidation since we'd have "less cluster churn" disrupting our current consolidation decision-making. |
/triage accepted |
Description
What problem are you trying to solve?
I have the following hypothesis.
I'd like to see this tested and documented. I suspect that in some cases, especially where eviction on some pods is disabled, that this would provide a significant price reduction.
How important is this feature to you?
I think having this officially documented would help users understand how to get the most out of Karpenter and would add weight to requests to cloud providers to support customising the scheduler.
The text was updated successfully, but these errors were encountered: