PSI-based node conditions

[roycaihw]

Enhancement Description

• One-line enhancement description (can be used as a release note): Introduce node conditions based on PSI metrics.
• Kubernetes Enhancement Proposal: KEP-5394: PSI-based node conditions #5395
• Discussion Link: The original PSI KEP Support PSI based on cgroupv2 #4205 contains two phases: 1) exposing PSI metrics and 2) PSI-based node conditions. This KEP is split from the original KEP to track phase 2, so that phase 1 and phase 2 can move at different paces. We plan to graduate phase 1 to Beta in 1.34. Phase 2 is yet to be developed and will stay Alpha in 1.34.
• PRs by stage and milestone:
  • Alpha - v1.34
    • KEP (k/enhancements) update PR(s): KEP-5394: PSI-based node conditions #5395
    • Code (k/k) update PR(s):
    • Docs (k/website) update(s):

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

/sig node
/stage alpha
/assign

[rayandas]

Hi @roycaihw Enhancements team here. Is this KEP planning for v1.34? If yes, you have to lead-opted-in, else release team won't be able to track this KEP.
Thanks!

[haircommander]

/label lead-opted-in
/milestone v1.34

I think this KEP should be used for using the PSI metrics, not for exposing them. 4205 should be for exposing them (as it already has been). I am opting in here though to put it on the board

[haircommander]

if we go along with ^ then it would be
/stage alpha

here

[fykaa]

Hello @roycaihw 👋, v1.34 Enhancements team here again.

Just checking in as we approach Enhancements Freeze on 21:00 UTC Friday 20th June 2025.

This enhancement is targeting stage alpha for v1.34 (correct me, if otherwise)

Here's where this enhancement currently stands:

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: v1.34.
• KEP readme has up-to-date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here). If your production readiness review is not completed yet, please make sure to fill the production readiness questionnaire in your KEP by the PRR Freeze deadline on { PRR_FREEZE_DATETIME } so that the PRR team has enough time to review your KEP.

For this KEP, we would just need to update the following:

• KEP merged to k/enhancements repo
• PRR completed and merged

The status of this enhancement is marked as At risk for enhancements freeze. Please keep the issue description up-to-date with appropriate stages as well.

If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you!