You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We’ve just launched a new project, the AWS Node Termination Handler that drains nodes during spot terminations.
The AWS Node Termination Handler provides a connection between termination requests from AWS infrastructure to Kubernetes nodes, allowing graceful draining and termination of nodes that receive interruption notifications. The termination handler uses the Kubernetes API to initiate drain and cordon actions on a node that is targeted for termination. The Node Termination Handler project can also be configured to simulate Spot termination requests to see how Kubernetes applications react to interruptions.
This project is open source (contributions welcome!) and supported by AWS. You can run the termination handler on any Kubernetes cluster running on AWS, including clusters created with Amazon Elastic Kubernetes Service (https://aws.amazon.com/eks/).
We’ve just launched a new project, the AWS Node Termination Handler that drains nodes during spot terminations.
The AWS Node Termination Handler provides a connection between termination requests from AWS infrastructure to Kubernetes nodes, allowing graceful draining and termination of nodes that receive interruption notifications. The termination handler uses the Kubernetes API to initiate drain and cordon actions on a node that is targeted for termination. The Node Termination Handler project can also be configured to simulate Spot termination requests to see how Kubernetes applications react to interruptions.
This project is open source (contributions welcome!) and supported by AWS. You can run the termination handler on any Kubernetes cluster running on AWS, including clusters created with Amazon Elastic Kubernetes Service (https://aws.amazon.com/eks/).
See more on the project project GitHub page (https://github.com/aws/aws-node-termination-handler).
The text was updated successfully, but these errors were encountered: