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
{{ message }}
This repository was archived by the owner on Jul 22, 2024. It is now read-only.
Copy file name to clipboardexpand all lines: README.md
+4-7
Original file line number
Diff line number
Diff line change
@@ -8,14 +8,11 @@ Utilise the power of AWS Auto Scaling group (ASG) lifecycle hooks and drain your
8
8
For each item received it contacts Kubernetes, taints the node to be shut down and evicts any pods not tolerant to the taint.
9
9
Meant to be run in side Kubernetes with a single replica only.
10
10
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
16
13
> 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!
19
16
20
17
## Use cases
21
18
*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