kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #884 from k82cn/rm_inode_cond 

Removed InodePressure condition.
This commit is contained in:
Klaus Ma 2017-08-08 19:27:13 +08:00 committed by GitHub
parent ce1d55e3cb bdba4b55a3
commit 85ddcc4af4
1 changed files with 0 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
contributors/design-proposals/taint-node-by-condition.md
View File

@ -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.