[service] [request]: EKS AutoMode does not support all spot allocation strategies
- Dominant language
- Shell
- Stars
- 5.4k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
### 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
**Tell us about your request**
What do you want us to build?
EKS AutoMode to support all spot allocation strategies. Not just `price-capacity-optimized`
**Which service(s) is this request for?**
This could be Fargate, ECS, EKS, ECR
EKS AutoMode specifically.
**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
What outcome are you trying to achieve, ultimately, and why is it hard/impossible to do right now? What is the impact of not having this problem solved? The more details you can provide, the better we'll be able to understand and solve the problem.
Supporting `capacity-optimized` and `lowest-price` spot allocation strategy would benefit users by providing more spot configuration options.
**Are you currently working around this issue?**
Just using the default spot allocation strategy: `price-capacity-optimized`
**Additional context**
Anything else we should know?
I realize spot allocation strategy is a single/small leverage in making spot more reliable. Having a large instance type diversity is arguably more important than the strategy; however, it would be useful to support all configuration options.
Contributor guide
Research direction
The request concerns EKS AutoMode spot allocation, which currently supports only `price-capacity-optimized`. Review the stated desired support for `capacity-optimized` and `lowest-price`; the issue names no repository files, tests, or implementation entry point. Done means EKS AutoMode supports those additional allocation strategies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100