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
+7-5Lines changed: 7 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -266,12 +266,15 @@ it.
266
266
267
267
#### Deprecation
268
268
269
+
<!--
269
270
- Announce deprecation and support policy of the existing flag
270
271
- Two versions passed since introducing the functionality that deprecates the flag (to address version skew)
271
272
- Address feedback on usage/changed behavior, provided on GitHub issues
272
273
- Deprecate the flag
273
274
-->
274
275
276
+
N/A
277
+
275
278
### Upgrade / Downgrade Strategy
276
279
277
280
No impact. Runc will be upgraded to 1.2.0 version as a prerequisite for this feature,
@@ -283,9 +286,6 @@ to a different kubelet version.
283
286
284
287
N/A
285
288
286
-
PSI stats will be available only after CRI and cadvisor have been updated to use runc 1.2.0
287
-
in K8s 1.29. Since `PSI Based Node Conditions` is dependent on kubelet version, and CRI and kubelet are generally updated in tandem, Version skew strategy is not applicable.
288
-
289
289
## Production Readiness Review Questionnaire
290
290
291
291
<!--
@@ -344,7 +344,9 @@ well as the [existing list] of feature gates.
344
344
Any change of default behavior may be surprising to users or break existing
345
345
automations, so be extremely careful here.
346
346
-->
347
-
TBD
347
+
No behavior change when there is no node level resource pressure.
348
+
349
+
When there is node level memory / IO pressure, the node will be marked with the corresponding resource pressure condition and taint, which will prevent new workloads from being scheduled to this node.
348
350
349
351
###### Can the feature be disabled once it has been enabled (i.e. can we roll back the enablement)?
350
352
@@ -516,7 +518,7 @@ and creating new ones, as well as about cluster-level services (e.g. DNS):
516
518
- Impact of its outage on the feature:
517
519
- Impact of its degraded performance or high-error rates on the feature:
518
520
-->
519
-
Yes, it depends on runc version 1.2.0. This KEP can be implemented only after runc 1.2.0 is released, which is estimated to be released in Q1 2024.
0 commit comments