From f603f26afabf54935daaa740d6cbc4169f7a8239 Mon Sep 17 00:00:00 2001
From: Sean Malloy <sean.malloy@kohls.com>
Date: Sun, 8 Mar 2020 22:30:51 -0500
Subject: [PATCH] Document Using Descheudler As a Remedy System

In addition to using draino as a remedy system the k8s descheduler can
also be used as a remedy system.
---
 README.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/README.md b/README.md
index e71c7baa..ad6602b3 100644
--- a/README.md
+++ b/README.md
@@ -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