Skip to content

Commit

Permalink
remove beta notice for queue-processor mode (#430)
Browse files Browse the repository at this point in the history
  • Loading branch information
bwagner5 authored May 11, 2021
1 parent daf7dd1 commit 0fa8d82
Showing 1 changed file with 1 addition and 2 deletions.
3 changes: 1 addition & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ The aws-node-termination-handler (NTH) can operate in two different modes: Insta

The aws-node-termination-handler **[Instance Metadata Service](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html) Monitor** will run a small pod on each host to perform monitoring of IMDS paths like `/spot` or `/events` and react accordingly to drain and/or cordon the corresponding node.

The aws-node-termination-handler **Queue Processor** will monitor an SQS queue of events from Amazon EventBridge for ASG lifecycle events, EC2 status change events, and Spot Interruption Termination Notice events. When NTH detects an instance is going down, we use the Kubernetes API to cordon the node to ensure no new work is scheduled there, then drain it, removing any existing work. The termination handler **Queue Processor** requires AWS IAM permissions to monitor and manage the SQS queue and to query the EC2 API. The queue processor mode is currently in a beta preview, but we'd love your feedback on it!
The aws-node-termination-handler **Queue Processor** will monitor an SQS queue of events from Amazon EventBridge for ASG lifecycle events, EC2 status change events, and Spot Interruption Termination Notice events. When NTH detects an instance is going down, we use the Kubernetes API to cordon the node to ensure no new work is scheduled there, then drain it, removing any existing work. The termination handler **Queue Processor** requires AWS IAM permissions to monitor and manage the SQS queue and to query the EC2 API.

You can run the termination handler on any Kubernetes cluster running on AWS, including self-managed clusters and those created with Amazon [Elastic Kubernetes Service](https://docs.aws.amazon.com/eks/latest/userguide/what-is-eks.html).

Expand Down Expand Up @@ -182,7 +182,6 @@ For a full list of configuration options see our [Helm readme](https://github.co
<details closed>
<summary>AWS Node Termination Handler - Queue Processor (requires AWS IAM Permissions)</summary>

## NOTE: THIS FUNCTIONALITY IS CURRENTLY IN BETA
<br>

### Infrastructure Setup
Expand Down

0 comments on commit 0fa8d82

Please sign in to comment.