v1.12.1

Changes

• Drop sqs messages for absent nodes #375 (thanks to Jason Haugen)
• Update stale.yml (thanks to Jillian Kuentz)
• Add support to override pod monitor namespace #372 (thanks to Victor Boissiere)
• helm: added necessary hostPorts in the PodSecurityPolicy #371 (thanks to Maxime VISONNEAU)
• Update README.md #370 (thanks to Brandon Wagner)
• Fix goreportcard test and run make fmt #369 (thanks to Jason Haugen)
• Sqs deletion issue 360 #364 (thanks to Andrew Zenk)
• Update stale.yml (thanks to Jillian Kuentz)
• clarify queue processor install instructions #366 (thanks to Bryan™)
• Avoid noisy error on scheduled events without NotAfter #363 (thanks to Tristan Keen)
• Update stale.yml #362 (thanks to Jillian Kuentz)
• Clarify podTerminationGracePeriod docs #351 (thanks to Gabe Gorelick)
• Document that deleteLocalData defaults to true, not false #350 (thanks to Gabe Gorelick)
• add sync readme to ecr public #345 (thanks to Bryan™)
• fix release prep for gh actions #343 (thanks to Bryan™)
• Update README.md #342 (thanks to Bryan™)
• Update Chart.yaml #341 (thanks to Bryan™)

v1.12.0

New Features 🎉

• Multithreaded event processor: NTH now supports parallel processing of events when using Queue-Processor mode! The number of processors can be configured via workers parameter described here. Thanks @universam1 #317

Improvements 🚀

• Add logic to publish images to ECR on release
• Fixes to improve release process

v1.11.2

Changes

• publish images to ecr public repo (#325)

v1.11.1

Bug Fixes 🐛

• fixed volume name of daemonsets to follow DNS-1123 standard: #300 thanks @n0gu
• fixed crashes on EC2 Instance State-change Notification events: #307 thanks @universam1
• added logLevel as a helm installation parameter #312
• fixed duplicate error checking #314

v1.11.0

New Features 🎉

• Adds configurable ManagedAsgTag option allowing users to run NTH in sqs queue processing mode across multiple clusters in an account (#272 thanks @blakestoddard & @paalkr)

Improvements

• Reduce NTH startup time across all modes via lowering IMDS retry rate (#281)

v1.10.0

Introducing EC2 Instance Rebalance Recommendation 🎉🎉🎉

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:

• IMDS Processor: --set enableRebalanceMonitoring=true
• Queue Processor: Create an Amazon EventBridge rule for EC2 Instance Rebalance Recommendations

Reference the Installation and Configuration sections of the ReadMe to learn more!

Other Changes:

• NTH Queue Processor mode now logs at debug level when a node termination event is received but the ASG is not tagged w/ the NTH managed tag aws-node-termination-handler/managed(Thanks to @kppullin #274)

AWS Node Termination Handler v1.9.0

🎊🎊🎊🎊🎊 NTH Queue Processing Mode (Preview) 🥳🥳🥳🥳🥳

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

Other Changes:

• The NTH DaemonSet in IMDS mode can now run with 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.html

AWS Node Termination Handler v1.8.0

Features:

1. Support for webhook templates (#253 thanks to @supasteev0 )
2. Improved logs
   • Better support of JSON logging
   • Log all pods when a node is cordoned (#257 thanks to @wanwenli )
   • Reduced log clutter from new events

Other Changes:

1. Upgraded Amazon EC2 Metadata Mock version to 1.6
2. Additional retries to improve stability
   • For IMDSv2 401 errors (#244 thanks to @DP19 )
   • For uncordoning nodes (#257 thanks to @nithu0115 )
3. New documentation on simulating interruptions with AEMM

AWS Node Termination Handler v1.7.0

Features:

1. Add availability zone to node metadata for use in webhook templates (#210 thanks to @DP19 )

Other Changes:

1. Moved to Amazon EC2 Metadata Mock for end-to-end tests.
2. Moved to go 1.15 and stripped debug tables from binary to make the image slightly smaller.
3. Added helm test to check template generation
4. Added retry logic for installing AEMM in tests to improve test stability

AWS Node Termination Handler v1.6.1

Bugs:

1. Fix helm chart error when deploying to EKS where semver comparison fails because of Minor version having a + on the end. (#195 thanks to @itssimon for reporting #193)
2. Do not schedule to fargate since it won't work correctly anyways (#191 thanks to @limed )
3. Fix incorrect flag description for --ignore-daemon-sets (#194 thanks to @takanabe )