Skip to content

Document the way the Kubernetes scheduler mode impacts Karpenter #1228

@stevehipwell

Description

@stevehipwell

Description

What problem are you trying to solve?
I have the following hypothesis.

With the default Kubernetes scheduler configuration of LeastAllocated, Karpenter is statistically more likely to disrupt pods and/or require consolidation than if the scheduler was running in MostAllocated mode.

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.

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    good first issueDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/documentationCategorizes issue or PR as related to documentation.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.triage/acceptedIndicates an issue or PR is ready to be actively worked on.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions