File tree 1 file changed +0
-10
lines changed
1 file changed +0
-10
lines changed Original file line number Diff line number Diff line change @@ -279,16 +279,6 @@ detected by the node-problem-detector. Remedy systems observe events and/or node
279
279
conditions emitted by the node-problem-detector and take action to return the
280
280
Kubernetes cluster to a healthy state. The following remedy systems exist:
281
281
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.
292
282
* [ ** Descheduler** ] ( https://github.com/kubernetes-sigs/descheduler ) strategy RemovePodsViolatingNodeTaints
293
283
evicts pods violating NoSchedule taints on nodes. The k8s scheduler's TaintNodesByCondition feature must
294
284
be enabled. The [ Cluster Autoscaler] ( https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler )
You can’t perform that action at this time.
0 commit comments