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
+18-1Lines changed: 18 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ stack, so Kubernetes will continue scheduling pods to the bad nodes.
26
26
To solve this problem, we introduced this new daemon **node-problem-detector** to
27
27
collect node problems from various daemons and make them visible to the upstream
28
28
layers. Once upstream layers have the visibility to those problems, we can discuss the
29
-
remedy system.
29
+
[remedy system](#remedy-systems).
30
30
31
31
# Problem API
32
32
node-problem-detector uses `Event` and `NodeCondition` to report problems to
@@ -138,6 +138,23 @@ For example, to test [KernelMonitor](https://github.com/kubernetes/node-problem-
138
138
- You can see more rule examples under [test/kernel_log_generator/problems](https://github.com/kubernetes/node-problem-detector/tree/master/test/kernel_log_generator/problems).
139
139
- For [KernelMonitor](https://github.com/kubernetes/node-problem-detector/blob/master/config/kernel-monitor.json) message injection, all messages should have ```kernel: ``` prefix (also note there is a space after ```:```).
140
140
141
+
# Remedy Systems
142
+
A _remedy system_ is a process or processes designed to attempt to remedy problems
143
+
detected by the node-problem-detector. Remedy systems observe events and/or node
144
+
conditions emitted by the node-problem-detector and take action to return the
145
+
Kubernetes cluster to a healthy state. The following remedy systems exist:
0 commit comments