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: keps/sig-node/5394-psi-node-conditions/README.md
+5-3Lines changed: 5 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -115,22 +115,22 @@ default threshold to be used for reporting the nodes under heavy resource pressu
115
115
116
116
**Note:** These actions are tentative, and will depend on different the outcome from testing and discussions with sig-node members, users, and other folks.
117
117
118
+
**Note:** In the initial Alpha implementation, we are not introducing node pressure condition for CPU. This is because unlike memory and IO, CPU is a compressible resource. See https://github.com/kubernetes/enhancements/issues/5062 for more details.
119
+
118
120
1. Introduce a new kubelet config parameter, pressure threshold, to let users specify the pressure percentage beyond which the kubelet would report the node condition to disallow workloads to be scheduled on it.
119
121
120
-
2. Add new node conditions corresponding to high PSI (beyond threshold levels) on CPU, Memory and IO.
122
+
2. Add new node conditions corresponding to high PSI (beyond threshold levels) on Memory and IO.
121
123
122
124
```go
123
125
// These are valid conditions of the node. Currently, we don't have enough information to decide
124
126
// node condition.
125
127
const (
126
128
…
127
129
// Conditions based on pressure at system level cgroup.
0 commit comments