aws / aws/aws-node-termination-handler
Host node awareness
Open
stalebot-ignore
Type: Enhancement
V2
- Dominant language
- Go
- Stars
- 1.8k
- Forks
- 286
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the feature**
NTH v2 should be aware of which node it's running on so that it can optimise the workflow for cordon/drain of that node, ideally so it exits cleanly.
**Is the feature request related to a problem?**
NTH will terminate itself leaving errors in the logs.
**Describe alternatives you've considered**
n/a
Contributor guide
Research direction
No files, tests, or entry points are named. Start by tracing the NTH v2 node termination workflow, especially cordon/drain handling, and determine how host-node awareness should support a clean exit; done means the handler avoids leaving errors when terminating on its own node.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go, kubernetes
- Domain
- cloud, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100