Gracefully handle EC2 instance shutdown within Kubernetes
actions_node
metric is deprecated due to the potential for high cardinality causing an issue for downstream consumers. A new metric actions
has been added to take the place of actions_node
without the potential for high cardinality. This release publishes both metrics but actions_node
will be removed in a future release.Full Changelog: https://github.com/aws/aws-node-termination-handler/compare/v1.20.0...v1.21.0
Full Changelog: https://github.com/aws/aws-node-termination-handler/compare/v1.19.0...v1.20.0
Full Changelog: https://github.com/aws/aws-node-termination-handler/compare/v1.18.3...v1.19.0
checkASGTagBeforeDraining
in end-to-end tests by @snay2 in https://github.com/aws/aws-node-termination-handler/pull/753
Full Changelog: https://github.com/aws/aws-node-termination-handler/compare/v1.18.2...v1.18.3
T.Setenv
to set env vars in tests by @Juneezee in https://github.com/aws/aws-node-termination-handler/pull/739
Full Changelog: https://github.com/aws/aws-node-termination-handler/compare/v1.18.1...v1.18.2
Full Changelog: https://github.com/aws/aws-node-termination-handler/compare/v2.0.0-alpha...v2.0.0-beta
Full Changelog: https://github.com/aws/aws-node-termination-handler/compare/v1.18.0...v1.18.1
v1.18.0
introduces the logFormatVersion
Helm chart option, to allow you to opt-in to more detailed logs.
The default value is 1
, which keeps logging the same way it did in prior releases (<= v1.17.3
).
Setting the value to 2
will give you more detail about which AWS event triggered the cordon/drain. Previously, all these events were bucketed under SQS_TERMINATE
and it was difficult to tell what was happening.
This option is also available as a command line flag, --log-format-version
logFormatVersion=2
modifies several Debug, Info, and Warn logs, as well as Kubernetes events emitted by NTH. These changes improve your observability about what NTH is doing when responding to events via SQS. If your monitoring system is configured to look for any of the specific strings in the tables below, you may need to modify your configuration to use the updated strings if you use the new log format version.
event_type
field from the Info log when starting a monitor; replace with monitor_type
field, with new values. See Table 1.event_type
field from the Warn log when a monitor fails to start; replace with monitor_type
field, with new values. See Table 1.monitor
field in the Info log. See Table 1.kind
field in the Info log, if running Queue Processor mode. See Table 2.SQS_TERMINATE
in the Debug log if running Queue Processor mode. See Table 2.Previous | New |
---|---|
REBALANCE_RECOMMENDATION |
REBALANCE_RECOMMENDATION_MONITOR |
SCHEDULED_EVENT |
SCHEDULED_EVENT_MONITOR |
SPOT_ITN |
SPOT_ITN_MONITOR |
SQS_TERMINATE |
SQS_MONITOR |
Previous | New |
---|---|
REBALANCE_RECOMMENDATION |
REBALANCE_RECOMMENDATION |
SCHEDULED_EVENT |
SCHEDULED_EVENT |
SPOT_ITN |
SPOT_ITN |
SQS_TERMINATE |
REBALANCE_RECOMMENDATION SCHEDULED_EVENT SPOT_ITN STATE_CHANGE ASG_LIFECYCLE |
Previous reason | New reason |
---|---|
RebalanceRecommendation |
RebalanceRecommendation |
ScheduledEvent |
ScheduledEvent |
SpotInterruption |
SpotInterruption |
SQSTermination |
RebalanceRecommendation ScheduledEvent SpotInterruption StateChange ASGLifecycle |
Full Changelog: https://github.com/aws/aws-node-termination-handler/compare/v1.17.3...v1.18.0
Full Changelog: https://github.com/aws/aws-node-termination-handler/compare/0ab461ddccdb602dca984a727ebfa417a7edcfe8...v2.0.0-alpha
Full Changelog: https://github.com/aws/aws-node-termination-handler/compare/v1.17.2...v1.17.3