Removed InodePressure condition.

yastij · Aug 8, 2017 · bdba4b5 · bdba4b5
1 parent fd8bc60
commit bdba4b5
Showing 1 changed file with 0 additions and 3 deletions.
diff --git a/contributors/design-proposals/taint-node-by-condition.md b/contributors/design-proposals/taint-node-by-condition.md
@@ -32,9 +32,6 @@ In addition to this, with taint-based-eviction, the Node Controller already tain
 |NetworkUnavailable  |True                | NoSchedule   | node.kubernetes.io/networkUnavailable |
 |                    |False               | -            | |
 |                    |Unknown             | -            | |
-|InodePressure       |True                | NoSchedule   | node.kubernetes.io/inodePressure      |
-|                    |False               | -            | |
-|                    |Unknown             | -            | |
 
 For example, if a CNI network is not detected on the node (e.g. a network is unavailable), the Node Controller will taint the node with `node.kubernetes.io/networkUnavailable=:NoSchedule`. This will then allow users to add a toleration to their `PodSpec`, ensuring that the pod can be scheduled to this node if necessary. If the kubelet did not update the node’s status after a grace period, the Node Controller will only taint the node with `node.kubernetes.io/unreachable`; it will not taint the node with any unknown condition.