[EKS] [request]: Leases for Fargate nodes remain after node termination
- 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
**Which service(s) is this request for?**
EKS
**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Leases for Fargate nodes are deleted when the node leave the cluster and are recreated just after.
Therefore leases for old Fargate nodes accumulate in the cluster.
**Are you currently working around this issue?**
We delete all leases in namespace kube-node-lease.
Contributor guide
Research direction
No source files, tests, or entry points are identified. Start by reviewing how EKS Fargate creates and removes Kubernetes Leases in the kube-node-lease namespace, then confirm the desired lifecycle with maintainers; done means leases for terminated Fargate nodes no longer accumulate or reappear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100