NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules, #1095 by repository stars
Latest stable
v1.25.6
Last release 28 days ago
20 Oct 2026
Ships fairly regularly
a new release about every 2 months
Nearly every release is documented
notes for 55 of 56 stable releases
Nothing withdrawn
no release was ever pulled
7 years old
133 releases · first in 2020
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Add and remove exclude-from-external-load-balancers label by @tjs-intel in https://github.com/aws/aws-node-termination-handler/pull/582
Full Changelog: https://github.com/aws/aws-node-termination-handler/compare/v1.15.0...v1.16.0
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Support ASG-to-SQS Lifecycle Termination events by @AustinSiu in https://github.com/aws/aws-node-termination-handler/pull/568
dnsConfig directive by @danquack in https://github.com/aws/aws-node-termination-handler/pull/571Full Changelog: https://github.com/aws/aws-node-termination-handler/compare/v1.14.1...v1.15.0
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Set enableProbesServer in queue processor mode release artifacts by @gabegorelick in https://github.com/aws/aws-node-termination-handler/pull/524
enableProbesServer in queue processor mode release artifacts by @gabegorelick in https://github.com/aws/aws-node-termination-handler/pull/524Full Changelog: https://github.com/aws/aws-node-termination-handler/compare/v1.14.0...v1.14.1
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Improve API efficiency and handling of unmanaged nodes by @mechanical-fish in https://github.com/aws/aws-node-termination-handler/pull/506
Full Changelog: https://github.com/aws/aws-node-termination-handler/compare/v1.13.4...v1.14.0
Nothing published for this version
feat(chart): Stop using hostPort on deployment #501 (thanks to Steve Hipwell)
fix k8s event patch permission and add test #480 (thanks to Brandon Wagner)
Nothing published for this version
fixes #423: Populate pod list in webhook notification #464 (thanks to Abhay Verma)
Nothing published for this version
Nothing published for this version
Nothing published for this version
add pods to webhook event and log pods on node #447 (thanks to Brandon Wagner)
Nothing published for this version
Nothing published for this version
Nothing published for this version
fixed and improved region detection within queue url #403 (thanks to Brandon Wagner)
Implement Liveness probe #389 (thanks to Yauheni Sliaptsou)
Nothing published for this version
Nothing published for this version
Nothing published for this version
Drop sqs messages for absent nodes #375 (thanks to Jason Haugen)
Multithreaded event processor: NTH now supports parallel processing of events when using Queue-Processor mode! The number of processors can be configu
workers parameter described here. Thanks @universam1 #317publish images to ecr public repo
fixed volume name of daemonsets to follow DNS-1123 standard: #300 thanks @n0gu
Adds configurable ManagedAsgTag option allowing users to run NTH in sqs queue processing mode across multiple clusters in an account (#272 thanks @bla
ManagedAsgTag option allowing users to run NTH in sqs queue processing mode across multiple clusters in an account (#272 thanks @blakestoddard & @paalkr)NTH v1.10.0 adds support for EC2 Instance Rebalance Recommendations, a notification directed towards Spot Instances that are at an elevated risk of in
NTH v1.10.0 adds support for EC2 Instance Rebalance Recommendations, a notification directed towards Spot Instances that are at an elevated risk of interruption!
For v1.10.0, upon receiving the Rebalance Recommendation, NTH will cordon the node only; however, we encourage users to submit feedback if more configuration flexibility is desired!
Start consuming this new notification today with these quick-start configurations:
--set enableRebalanceMonitoring=trueEC2 Instance Rebalance RecommendationsReference the Installation and Configuration sections of the ReadMe to learn more!
aws-node-termination-handler/managed(Thanks to @kppullin https://github.com/aws/aws-node-termination-handler/pull/274)This release adds support for a new mode of operation for NTH called queue-processor. Until now, NTH has operated by monitoring the EC2 Instance Metad
This release adds support for a new mode of operation for NTH called queue-processor. Until now, NTH has operated by monitoring the EC2 Instance Metadata Service (IMDS) for spot ITN events and EC2 scheduled maintenance events. The new queue-processor mode allows NTH to respond to more events like ASG lifecycle hooks, EC2 state changes, and Spot ITNs by sourcing events from Amazon EventBridge + Amazon SQS.
The new queue-processor mode is a preview and is not meant for production environments right now. However, we would love for you to try it out on your test clusters. GA support will follow very soon!
Check out the readme on how to get started with NTH queue-processing mode https://github.com/aws/aws-node-termination-handler#installation-and-configuration
host_networking=false. The default still uses host networking, but if you'd like to run NTH outside the root network namespace, make sure that IMDSv2 IP hops are configure to 2 instead of the default 1 OR make sure IMDSv1 is still enabled. https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/configuring-instance-metadata-service.htmlOne column per quarter.