Skip to content

Add Resource Health Status to the Pod Status for Device Plugin and DRA #4680

Open

Description

@SergeyKanzhelev

Enhancement Description

/sig node

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

Activity

  1. added
    sig/nodeCategorizes an issue or PR as relevant to SIG Node.
    on May 31, 2024
  2. SergeyKanzhelev commented on May 31, 2024

    @SergeyKanzhelev
    MemberAuthor

    Discussed with @mrunalp and we fine to add this to milestone:

    /milestone v1.31
    /label lead-opted-in
    /stage alpha

  3. added
    stage/alphaDenotes an issue tracking an enhancement targeted for Alpha status
    on May 31, 2024
  4. added this to the v1.31 milestone on May 31, 2024
  5. ArkaSaha30 commented on Jun 4, 2024

    @ArkaSaha30
    Member

    Hello, @SergeyKanzhelev 👋, Enhancements team here.

    Just checking in as we approach enhancements freeze on 02:00 UTC Friday 14th June 2024 / 19:00 PDT Thursday 13th June 2024..

    This enhancement is targeting stage alpha for v1.31 (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.31. KEPs targeting stable will need to be marked as implemented after code PRs are merged and the feature gates are removed.
    • 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 so that the PRR team has enough time to review your KEP before the enhancements freeze.

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

    • Attach the PR link for the KEP with the relevant details along with PRR and get it merged

    The status of this enhancement is marked as at risk for enhancement 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!

  6. moved this to At Risk for Enhancements Freeze in 1.31 Enhancements Trackingon Jun 4, 2024
  7. jpbetz commented on Jun 11, 2024

    @jpbetz
    Contributor

    PRR reviewer here. Is there a KEP to review? Only a few days left till enhancements freeze..

  8. SergeyKanzhelev commented on Jun 12, 2024

    @SergeyKanzhelev
    MemberAuthor

    PRR reviewer here. Is there a KEP to review? Only a few days left till enhancements freeze..

    Yes, we have polished some imlpementation details, but from PRR perspective it is very straightforward

  9. richabanker commented on Jun 12, 2024

    @richabanker
    Contributor

    Looks like this is the KEP PR: #4681

  10. SergeyKanzhelev commented on Jun 13, 2024

    @SergeyKanzhelev
    MemberAuthor

    @ArkaSaha30 this KEP can be marked as done for all the checkboxes you listed. Thank you!

  11. dipesh-rawat commented on Jun 13, 2024

    @dipesh-rawat
    Member

    Hello @SergeyKanzhelev 👋, 1.31 Enhancements team here,

    Now that PR #4681 has been merged, all the KEP requirements in place and merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze. 🚀

    The status of this enhancement is marked as tracked for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

  12. moved this from At Risk for Enhancements Freeze to Tracked for Enhancements Freeze in 1.31 Enhancements Trackingon Jun 13, 2024
  13. 276 remaining items

  14. harche commented on Jul 27, 2026

    @harche
    Contributor

    Hello @harche @ArangoGutierrez @SergeyKanzhelev 👋🏻 v1.37 Docs Team here!
    Does this enhancement work planned for v1.37 require any new docs or modification to existing docs?

    Thanks @kernel-kun for reaching out, there is not doc update for 1.37 for this feature.

  15. moved this from Exception Approved to At Risk for Docs Freeze in v1.37 Release Trackingon Jul 27, 2026
  16. moved this from At Risk for Docs Freeze to Tracked for Docs Freeze in v1.37 Release Trackingon Jul 27, 2026
  17. SwathiR03 commented on Jul 29, 2026

    @SwathiR03

    Hi, @harche @ArangoGutierrez @SergeyKanzhelev ! I see this KEP has been added in post code-freeze. Since it is DRA-related, there is a DRA feature blog being actively worked on: kubernetes/website#56351 Will this KEP also be talking part?

  18. harche commented on Jul 29, 2026

    @harche
    Contributor

    Hi, @harche @ArangoGutierrez @SergeyKanzhelev ! I see this KEP has been added in post code-freeze. Since it is DRA-related, there is a DRA feature blog being actively worked on: kubernetes/website#56351 Will this KEP also be talking part?

    Thanks @SwathiR03 for reaching out, we don't have any blog post for this cycle for this feature.

  19. karimzakzouk commented on Aug 18, 2026

    @karimzakzouk
    Member

    Hi @SergeyKanzhelev @harche @ArangoGutierrez 👋, v1.37 Enhancements Shadow here,

    Given that this KEP has graduated to stable, if all the work is completed, could you please update the KEP status in kep.yaml to implemented, and then close this issue?

    Thanks!

  20. harche commented on Aug 19, 2026

    @harche
    Contributor

    Given that this KEP has graduated to stable, if all the work is completed, could you please update the KEP status in kep.yaml to implemented, and then close this issue?

    Hi @karimzakzouk, thanks for checking in. That reading is not quite right. This KEP has not graduated to stable. It is still in beta.

    kep.yaml still has status: implementable, not implemented. The current stage is stage: beta, with latest-milestone: v1.36. The stable: v1.37 value is only the target, not a completed graduation.

    In kubernetes/kubernetes, ResourceHealthStatus is Alpha in 1.31 and Beta (default on) in 1.36. There is no GA or LockToDefault entry. The same is true for ResourceHealthStatusMessage.

    The last promotion was to beta for 1.36 (enhancements#5689, kubernetes#135255). There is no GA promotion PR.

    The stage/stable label on this issue means we are targeting stable this cycle, not that it already GAed. Please keep this issue open. We should not set status: implemented or close it until the feature actually graduates.

    Thanks!

  21. karimzakzouk commented on Aug 19, 2026

    @karimzakzouk
    Member

    Hey @harche , you're right, my bad on the previous comment. I read the stage/stable label as "graduated" but it's the target for the cycle, not the current state.
    Treating it as the default cleanup case instead:

    We are nearing the close of the v1.37 release. As part of cleanup, we are removing the lead-opted-in and tracked/* labels and milestone to prepare for the next cycle.

    If you would like to work on this enhancement in v1.38, please have the SIG lead opt in by adding the lead-opted-in label and setting the milestone using /milestone v1.38, which will ensure it gets added to the tracking board for next release.

    Thanks for catching it!

    /remove-label lead-opted-in
    /remove-label tracked/yes
    /remove-label tracked/no
    /milestone clear

  22. kubernetes-prow commented on Aug 19, 2026

    @kubernetes-prow
    Contributor

    @karimzakzouk: Those labels are not set on the issue: lead-opted-in, tracked/yes, tracked/no

    Details

    In response to this:

    Hey @harche , you're right, my bad on the previous comment. I read the stage/stable label as "graduated" but it's the target for the cycle, not the current state.
    Treating it as the default cleanup case instead:

    We are nearing the close of the v1.37 release. As part of cleanup, we are removing the lead-opted-in and tracked/* labels and milestone to prepare for the next cycle.

    If you would like to work on this enhancement in v1.38, please have the SIG lead opt in by adding the lead-opted-in label and setting the milestone using /milestone v1.38, which will ensure it gets added to the tracking board for next release.

    Thanks for catching it!

    /remove-label lead-opted-in
    /remove-label tracked/yes
    /remove-label tracked/no
    /milestone clear

    Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

  23. harche commented on Aug 19, 2026

    @harche
    Contributor

    @SergeyKanzhelev @haircommander, following up on the v1.37 cleanup in #4680 (comment). Could you please opt this KEP in for v1.38?

    This KEP is still in beta (ResourceHealthStatus / ResourceHealthStatusMessage, on by default since 1.36). We are targeting stable. Last cycle we pulled the 1.37 opt-in after @johnbelamaric pointed out that no DRA driver had adopted the API yet.

    That gap is now closing:

    If you are okay with opting this in, would you be able to add /label lead-opted-in and /milestone v1.38? If you are also comfortable targeting GA this cycle, /stage stable would be appreciated as well.

  24. moved this from 🔖 Ready to 🏗 In progress in Dynamic Resource Allocationon Aug 25, 2026
  25. moved this from 🏗 In progress to 📋 Backlog in Dynamic Resource Allocationon Aug 25, 2026
  26. moved this from Triage to Not for release in SIG Node 1.38 KEPs planningon Sep 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

sig/nodeCategorizes an issue or PR as relevant to SIG Node.stage/stableDenotes an issue tracking an enhancement targeted for Stable/GA statuswg/device-managementCategorizes an issue or PR as relevant to WG Device Management.

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions