Skip to content

Commit d6cfed9

Browse files
authored
Removed draino from README
The draino project was not updated for 5 years.
1 parent 01e1cf0 commit d6cfed9

File tree

1 file changed

+0
-10
lines changed

1 file changed

+0
-10
lines changed

README.md

-10
Original file line numberDiff line numberDiff line change
@@ -279,16 +279,6 @@ detected by the node-problem-detector. Remedy systems observe events and/or node
279279
conditions emitted by the node-problem-detector and take action to return the
280280
Kubernetes cluster to a healthy state. The following remedy systems exist:
281281

282-
* [**Draino**](https://github.com/planetlabs/draino) automatically drains Kubernetes
283-
nodes based on labels and node conditions. Nodes that match _all_ of the supplied
284-
labels and _any_ of the supplied node conditions will be prevented from accepting
285-
new pods (aka 'cordoned') immediately, and
286-
[drained](https://kubernetes.io/docs/tasks/administer-cluster/safely-drain-node/)
287-
after a configurable time. Draino can be used in conjunction with the
288-
[Cluster Autoscaler](https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler)
289-
to automatically terminate drained nodes. Refer to
290-
[this issue](https://github.com/kubernetes/node-problem-detector/issues/199)
291-
for an example production use case for Draino.
292282
* [**Descheduler**](https://github.com/kubernetes-sigs/descheduler) strategy RemovePodsViolatingNodeTaints
293283
evicts pods violating NoSchedule taints on nodes. The k8s scheduler's TaintNodesByCondition feature must
294284
be enabled. The [Cluster Autoscaler](https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler)

0 commit comments

Comments
 (0)