aws / aws/containers-roadmap

[EKS/Fargate] [request]: Support Fargate Spot for EKS

Open
#622 66 comments 1782 reactions 0 assignees View on GitHub
EKS Fargate Proposed
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**
Provide the option to select `FARGATE_SPOT` as the Fargate Provider when creating an EKS Fargate Profile, like in ECS.

**Which service(s) is this request for?**
EKS, Fargate

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Cost optimization and lower administration overhead for interruption tolerant workloads on EKS.

**Are you currently working around this issue?**
Yes, by using EC2 Spot Fleets.

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the EKS Fargate Profile provider option and the ECS Fargate Spot behavior named in the request. Compare these with the EC2 Spot Fleet workaround and define what selecting FARGATE_SPOT should enable for interruption-tolerant workloads. Done means the requested provider is supported for EKS Fargate Profiles and its behavior is documented.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.