[EKS] [request]: Graceful node termination for self managed nodes

<!--- Please keep this note for the community ---> ### 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 <!--- Thank you for keeping this note for the community ---> **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

Posted by mikestef9 on Mar 9, 2020, 10:05 PM

Tags

• support (Software)

Related issues

• Add 65536 size support for maps
• TypeScript 7.1 Iteration Plan
• nvim-treeconfig: upstream nvim-treesitter
• Add the "action" and "method" attributes to <button>
• [FEATURE] Support multiple Connector accounts (same connector, different accounts) in Claude and Claude Code on the web (claude.ai/code)
• > We were imposed GitHub for so many exercises!