Skip to content

Commit

Permalink
Document Using Descheudler As a Remedy System
Browse files Browse the repository at this point in the history
In addition to using draino as a remedy system the k8s descheduler can
also be used as a remedy system.
  • Loading branch information
seanmalloy committed Mar 9, 2020
1 parent 4ad6227 commit f603f26
Showing 1 changed file with 4 additions and 0 deletions.
4 changes: 4 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -248,6 +248,10 @@ Kubernetes cluster to a healthy state. The following remedy systems exist:
to automatically terminate drained nodes. Refer to
[this issue](https://github.com/kubernetes/node-problem-detector/issues/199)
for an example production use case for Draino.
* [**Descheduler**](https://github.com/kubernetes-sigs/descheduler) strategy RemovePodsViolatingNodeTaints
evicts pods violating NoSchedule taints on nodes. The k8s scheduler's TaintNodesByCondition feature must
be enabled. The [Cluster Autoscaler](https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler)
can be used to automatically terminate drained nodes.

# Testing

Expand Down

0 comments on commit f603f26

Please sign in to comment.