diff options
| -rw-r--r-- | contributors/design-proposals/taint-node-by-condition.md | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/contributors/design-proposals/taint-node-by-condition.md b/contributors/design-proposals/taint-node-by-condition.md index 439a6660..35a5ee2d 100644 --- 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. |