Skip to content

Commit f603f26

Browse files
committed
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.
1 parent 4ad6227 commit f603f26

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

README.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -248,6 +248,10 @@ Kubernetes cluster to a healthy state. The following remedy systems exist:
248248
to automatically terminate drained nodes. Refer to
249249
[this issue](https://github.com/kubernetes/node-problem-detector/issues/199)
250250
for an example production use case for Draino.
251+
* [**Descheduler**](https://github.com/kubernetes-sigs/descheduler) strategy RemovePodsViolatingNodeTaints
252+
evicts pods violating NoSchedule taints on nodes. The k8s scheduler's TaintNodesByCondition feature must
253+
be enabled. The [Cluster Autoscaler](https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler)
254+
can be used to automatically terminate drained nodes.
251255

252256
# Testing
253257

0 commit comments

Comments
 (0)