[Fargate] [request]: Make deleting Fargate profiles faster
- 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**
Please make it faster to delete fargate-profiles. They can only be deleted serially, and I've seen individual profiles take upwards of 20 minutes to delete.
**Which service(s) is this request for?**
Fargate
**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
We're working on orchestrating many EKS clusters with automation (Terraform). Slow fargate-profile deletion absolutely kills our ability to iterate quickly.
**Are you currently working around this issue?**
No. Our Terraform code has huge timeouts to avoid errors, but there seems to be no way to get around it when a profile takes >20m to delete. (Seems to happen about 50% of the time.)
**Additional context**
The only documentation I've found about how long it should take is "Note that the profile deletion is a process that can take up to a few minutes." [here](https://eksctl.io/usage/fargate-support/#managing-fargate-profiles). The fact that it can take upwards of 20m should be well-documented everywhere!
**Attachments**
[none]
Contributor guide
Research direction
Start by reviewing the reported Fargate profile deletion behavior in the context of Terraform-managed EKS clusters, along with the eksctl Fargate support documentation linked in the issue. Done means deletion is substantially faster or no longer serially blocking automation, and the documented expected duration matches reality.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, terraform
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100