[EKS] [request]: enable graceful node shutdown
- 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**
EKS changelog (https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html) seems to indicate tha graceful node shutdown is enabled on EKS 1.21. However, unless I’m mistaken, this is not the case. Could you consider enabling it?
**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?**
Without graceful node shutdown nor aws-node-termination-handler, an EKS cluster cannot take preventive actions in response to events which lead to instance shutdown (like ASG AZ rebalance, ASG instance refresh, spot instance preemption, etc). This can lead to service disruptions. Enabling graceful node shutdown would provide an out of the box solution.
**Are you currently working around this issue?**
No.
**Additional context**
ASG AZ rebalance can happen after a scale-down made by the cluster autoscaler.
Contributor guide
Research direction
Start with the EKS changelog linked in the issue and compare its statement about graceful node shutdown on EKS 1.21 with the reported behavior. Review how EKS handles ASG AZ rebalance, instance refresh, and Spot preemption, along with the aws-node-termination-handler workaround. Done means graceful node shutdown is enabled or the changelog and supported behavior clearly match.
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
- Needs clarification
- Newbie friendliness
- 25/100