Skip to content
This repository was archived by the owner on Jul 22, 2024. It is now read-only.

Commit 658399a

Browse files
authored
Merge pull request #323 from rebuy-de/add-deprecation-notice
2 parents a3ea840 + 5893eba commit 658399a

File tree

1 file changed

+4
-7
lines changed

1 file changed

+4
-7
lines changed

README.md

+4-7
Original file line numberDiff line numberDiff line change
@@ -8,14 +8,11 @@ Utilise the power of AWS Auto Scaling group (ASG) lifecycle hooks and drain your
88
For each item received it contacts Kubernetes, taints the node to be shut down and evicts any pods not tolerant to the taint.
99
Meant to be run in side Kubernetes with a single replica only.
1010

11-
> **Development Status** *node-drainer* is designed for internal use only.
12-
> Expect breaking changes any time, but if you experience any issue, feel free
13-
> to open an issue anyway.
14-
>
15-
> :fire: Consider using the [AWS Node Termination
11+
> **Development Status** *node-drainer* was designed for internal use only.
12+
> After migrating to AWS EKS we started to use the [Node Termination
1613
> Handler](https://github.com/aws/aws-node-termination-handler), which is the
17-
> official tool from AWS. It has better support and we will probably migrate
18-
> to it ourselves, if we experience a bigger roadblock with node-drainer.
14+
> official tool from AWS. Development for *node-drainer* was therefore stopped,
15+
> but feel free to fork and continuing its legacy!
1916
2017
## Use cases
2118
*node-drainer* is useful whenever any of the Kubernetes worker nodes running in AWS must be shut down. Graceful eviction of Kubernetes pods from terminated nodes ensures continuous operation of services when:

0 commit comments

Comments
 (0)