mirror of
https://github.com/kubernetes/node-problem-detector.git
synced 2026-02-14 18:09:57 +00:00
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.
This commit is contained in:
@@ -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
|
||||
|
||||
|
||||
Reference in New Issue
Block a user