Releases: aws/aws-node-termination-handler
AWS Node Termination Handler v1.6.1
Bugs:
- 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) - Do not schedule to fargate since it won't work correctly anyways (#191 thanks to @limed )
- Fix incorrect flag description for
--ignore-daemon-sets
(#194 thanks to @takanabe )
AWS Node Termination Handler v1.6.0
New Features: 🥳 🎉 🎊
- Experimental Windows support! (#185 thanks to @cjerad )
- Support specifying the Webhook URL in a K8s secret (#179 thanks to @imuqtadir and @farshad-hobsons for suggesting this feature #170)
- Support adding pod labels in the helm chart (#180 thanks to @mwconceicao)
Bugs:
- Do not fail on scheduled maintenance event when no end date is present (#182 thanks to @yzargari for reporting #147)
- Fix typo in prometheus metrics for "pre-drain" (#184 thanks to @zuzzas)
Docs:
- Adds a section in the readme on how to use aws-node-termination-handler with Kiam (#188 thanks to @leosunmo)
Tests:
- Added eks driver for e2e tests on windows nodes
AWS Node Termination Handler v1.5.0
New Features:
- Optionally taint nodes when a termination event or maintenance event is triggered (#162 thanks to @diversario)
- Optionally enable a prometheus metrics endpoint (#172 thanks to @manute)
Tests:
- Added end-to-end tests for tainting nodes
- Added end-to-end tests for prometheus metrics
AWS Node Termination Handler v1.4.0
New Features:
- Supports HTTP(S) proxying for webhooks (#150)
- Supports optional JSON logging (#152)
- Supports an optional cordon-only which only marks the node as unschedulable and does not drain the pods off the node. (#145)
- Removed unneeded K8s permissions given to aws-node-termination-handler in its cluster role. (#140)
- Tolerate all taints by default so that aws-node-termination-handler is launched everywhere. (#128)
Bug Fixes:
- Fixed a bug where Scheduled Maintenance Events start and end times could not be parsed when the day was a single digit. (#148)
- Fixed a bug where Scheduled Maintenance Event cancellations fail because of an alternative spelling of "canceled". (#133)
Tests:
- Added end-to-end tests for webhook HTTP proxy
- Added end-to-end tests for cordon-only feature
- Upgraded to Kind (Kubernetes-in-Docker) to version 0.8.1 for e2e tests.
AWS Node Termination Handler v1.3.1
Bug Fixes:
- Fixes a leak in the http client configuration
AWS Node Termination Handler v1.3.0
New Features:
- Supports IMDSv2
- Supports additional node metadata to construct more detailed webhook notifications. (#94)
Bug Fixes:
- Fixed IMDS parsing of Spot ITN events and added more IMDS requests to fill in node metadata that was not being returned by the Spot ITN response (#104).
Tests:
- Unit test coverage extended
AWS Node Termination Handler v1.2.0
New Features:
-
NTH now responds to EC2 instance scheduled maintenance events! This feature is experimental, and is by default disabled. You can enable it by using the
--enable-scheduled-event-draining
argument (or the correspondingENABLE_SCHEDULED_EVENT_DRAINING
environment variable). Once enabled, NTH will drain the node before the maintenance window begins. In addition, if a system-reboot maintenance event is received, NTH will add a label to your node and uncordon after the reboot has taken place. Read more about scheduled maintenance events here: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/monitoring-instances-status-check_sched.html -
Webhooks are now supported!
Tests:
- More e2e tests were added for scheduled maintenance events and webhooks
- Unit tests added
AWS Node Termination Handler v1.1.0
New Features:
- NTH now allows you to configure how long before the termination event you would like to start draining the node. Use the
--node-termination-grace-period
argument (orNODE_TERMINATION_GRACE_PERIOD
environment variable) to configure this new functionality. The default value will maintain the same functionality as v1.0.0 which is 120 seconds before the termination event.
Changes:
- Deprecated the "grace-period" argument in favor of "pod-termination-grace-period". Old configurations will still work using "grace-period" but a warning will be logged.
Tests:
- Kind was updated to the latest v0.6.0 for E2E tests.
- Tests were broken up into reusable scripts to facilitate more tests with less code
- goimports test was added to the go-report-card test
AWS Node Termination Handler v1.0.0
This release offers the node termination behavior of cordon and draining nodes if they receive a EC2 Spot Instance termination notification (ITN).
Features:
- Detect Spot ITN then use Kubernetes API to cordon and drain
- Retry mechanism for transient network issues connecting to metadata service
- Optional Ignore Daemonsets
- Optional Delete-Local-Data
- Optional Node Selector
- Optional Dry-Run Mode
- Integration testing framework