You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+5
Original file line number
Diff line number
Diff line change
@@ -287,6 +287,11 @@ Kubernetes cluster to a healthy state. The following remedy systems exist:
287
287
evicts pods violating NoSchedule taints on nodes. The k8s scheduler's TaintNodesByCondition feature must
288
288
be enabled. The [Cluster Autoscaler](https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler)
289
289
can be used to automatically terminate drained nodes.
290
+
*[**mediK8S**](https://github.com/medik8s) is an umbrella project for automatic remediation
291
+
system build on [Node Health Check Operator (NHC)](https://github.com/medik8s/node-healthcheck-operator) that monitors
292
+
node conditions and delegates remediation to external remediators using the Remediation API.[Poison-Pill](https://github.com/medik8s/poison-pill)
293
+
is a remediator that will reboot the node and make sure all statefull workloads are rescheduled. NHC supports conditionally remediating if the cluster
294
+
has enough healthy capacity, or manually pausing any action to minimze cluster disruption.
0 commit comments