Options for specifying AWS EC2 fleet allocation strategy
**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. <!-- Please keep this note for the community --> ### Community Note * Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) 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 <!-- Thank you for keeping this note for the community -->
Posted by literalice on Jan 30, 2022, 11:33 AM
Tags
Related issues
- >Beef is already too expensive for most people.
- I gave this a go a couple of years ago.
- I haven't seen any use cases around me, although I'm not that advanced user.
- [BUG] Pro Max 5x Quota Exhausted in 1.5 Hours Despite Moderate Usage
- > Unfortunately it doesn't offer free hosting for hobbyists.
- Still the same HID remapping project from last month (I was hoping to be done by now, but hardware is hard): https://github.co...
Raise real-world problems, find people facing the same issue, and discuss solutions.2,500 issues0 comments
pricing (Software)
>Beef is already too expensive for most people.
I gave this a go a couple of years ago.
I haven't seen any use cases around me, although I'm not that advanced user.
[BUG] Pro Max 5x Quota Exhausted in 1.5 Hours Despite Moderate Usage
> Unfortunately it doesn't offer free hosting for hobbyists.
Still the same HID remapping project from last month (I was hoping to be done by now, but hardware is hard): https://github.co...
This criticism seems like a complete non-sequitur to me.
Bring back the GitHub Copilot in the CLI commands to not break workflows
Options for specifying AWS EC2 fleet allocation strategy
**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. <!-- Please keep this note for the community --> ### Community Note * Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) 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 <!-- Thank you for keeping this note for the community -->
Comments (0)
No comments yet. Start the discussion.