[EKS] [request]: Graceful node termination for self managed nodes
- 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**
Graceful node termination handling for self managed nodes
**Which service(s) is this request for?**
This could be Fargate, ECS, EKS, ECR
**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
When an instance is terminated from an autoscaling event, we want to automatically detect that event and be able gracefully drain the node
**Additional context**
EKS Managed Node Groups support this functionality. This issue is tracking the feature request outside of managed node groups. This may be implemented through the AWS Node Termination Handler project (which already supports Spot termination handling)
https://github.com/aws/aws-node-termination-handler/issues/14
Contributor guide
Research direction
Start by reviewing the EKS managed node group behavior referenced in the issue and AWS Node Termination Handler issue 14. Determine how self-managed nodes should detect autoscaling termination and gracefully drain, then validate that the behavior covers the requested non-managed-node case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100