Skip to content

Options for specifying AWS EC2 fleet allocation strategy #1240

Open
@literalice

Description

@literalice

Tell us about your request

Adding options for specifying EC2 fleet allocation strategy by users.

Currently it's automatically decided by Karpenter:

  • capacity-optimized-prioritized - spot
  • lowest-price - on-demand

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Specifying other strategies by users should be useful especially in case of cost-sensitive workloads.
Currently Karpenter has no option for this so what the users only can do is to build their own controller from the source.

Are you currently working around this issue?
There is no work around now.

Additional context
I posted a PR for this issue: #1238 .
Would you like to use the PR for the basis of discussions.

Community Note

  • 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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

cost-optimizationfeatureNew feature or requestpriority/awaiting-more-evidenceLowest priority. Possibly useful, but not yet enough support to actually get it done.triage/acceptedIndicates that the issue has been accepted as a valid issue

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions