aws-node-termination-handler
aws-node-termination-handler copied to clipboard
Gracefully handle EC2 instance shutdown within Kubernetes
I took advantage of the rare incidence of a scheduled event on a node in our test EKS cluster to update to the latest NTH (1.12.0 via latest helm chart),...
**Describe the feature** Karpenter nodes are not bound to a Autoscaling Group. Filter on `tags` via `check-asg-tag-before-draining` is scoped to ASG only, so it is not possible to filter nodes...
**Describe the bug** When running the end-to-end tests on Kubernetes server version 1.23, I get the following warning: ``` policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+ ``` **Steps...
Events like spot rebalance recommendation, asg lifecycle hooks, spot ITN, and ec2 instance status change can cause multiple webhooks to fire, one for each event on the same instance. NTH...
NTH Queue-Processor should catch the ASG Launch Lifecycle Hook and complete it once the node has joined the k8s cluster successfully. Since ASG considers the instance ready when EC2 health...
**Describe the feature** when deciding if a node should be terminates (for example for scheduled maintainance) we want to say "don't do it now if the cluster is in trouble"...
We've noticed in our production environment that we have a need for something to deregister nodes from load balancers as part of the draining procedure, before the instance is terminated....
## Problem Our current integration test suite is written in Bash and is becoming difficult to maintain. We would like to be able to support more diverse cluster types and...
**Describe the feature** I'd like NTH to be able to group nodes (similar to the CA `--balance-similar-node-groups`) and support processing `n` nodes per group (this can still be constrained by...
**Describe the feature** When using NTH in queue mode we need to create EventBridge rules to match our resources. The examples don't have any filters but this isn't going to...