Repository navigation
Open
Labels
sig/nodeCategorizes an issue or PR as relevant to SIG Node.Categorizes an issue or PR as relevant to SIG Node.stage/stableDenotes an issue tracking an enhancement targeted for Stable/GA statusDenotes an issue tracking an enhancement targeted for Stable/GA statuswg/device-managementCategorizes an issue or PR as relevant to WG Device Management.Categorizes an issue or PR as relevant to WG Device Management.
Description
Enhancement Description
- One-line enhancement description (can be used as a release note): Expose device health information thru the Pod Status
- Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/4680-add-resource-health-to-pod-status/README.md
- Discussion Link: https://docs.google.com/document/d/1fOx4PTN61sDv6u9C-t-WpOH8hi2IpenJWPc-Za8UAQE/edit#heading=h.1tvyczqnfmzb (presented at WG Serving and WG Device Management)
- Primary contact (assignee): @harche
- Responsible SIGs: sig/node
/sig node
- Enhancement target (which target equals to which milestone):
- Alpha release target (x.y): 1.31
- Alpha2 release target (x.y): 1.34
- Beta release target (x.y): 1.36
- Stable release target (x.y): TBD
- Alpha
- KEP (
k/enhancements) update PR(s): KEP-4680: Add Resource Health Status to the Pod Status for Device Plugin and DRA #4681 - Code (
k/k) update PR(s): Implement resource health in pod status (KEP 4680) kubernetes#126243 - Docs (
k/website) update PR(s): Device plugin failures: KEP docs website#47029
- KEP (
- Alpha2 (DRA support)
- KEP (
k/enhancements) update PR(s): - Code (
k/k) update PR(s): - Docs (
k/website) update PR(s):
- KEP (
- Beta
- KEP (
k/enhancements) update PR(s): - Code (
k/k) update PR(s):- Fix bug in reporting health for templated and renamed DRA claims kubernetes#134875
- DRA: Add configurable health check timeout per device kubernetes#135147
- KEP-4680: apply Health status to pods that have already terminated kubernetes#135202
- KEP-4680: Add message field support to DRA device health reporting kubernetes#135196
- KEP-4680: Add tests to validate ShareID does not interfere with DRA Resource Health Status kubernetes#136758
- Docs (
k/website) update(s): [KEP-4680]: Update ResourceHealthStatus documentation for Beta in v1.36 website#54420
- KEP (
Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.
Reacted by Marcelo Barbosa, Rigel., Carlos Eduardo Arango Gutierrez, Zhifei Zhang, Tim Bannister and x0rw
Metadata
Metadata
Assignees
Labels
sig/nodeCategorizes an issue or PR as relevant to SIG Node.Categorizes an issue or PR as relevant to SIG Node.stage/stableDenotes an issue tracking an enhancement targeted for Stable/GA statusDenotes an issue tracking an enhancement targeted for Stable/GA statuswg/device-managementCategorizes an issue or PR as relevant to WG Device Management.Categorizes an issue or PR as relevant to WG Device Management.
Type
Projects
- StatusShow more project fields📋 Backlog
- StatusShow more project fieldsNot for release
- StatusShow more project fieldsTracked for Doc Freeze
- StatusShow more project fieldsDone
- StatusShow more project fieldsTracked for code freeze
- StatusShow more project fieldsRemoved from Milestone
- StatusShow more project fieldsRemoved
- StatusShow more project fieldsTracked for code freeze
- StatusShow more project fieldsDone
- StatusShow more project fieldsRemoved
- StatusShow more project fieldsRemoved from Milestone
- StatusShow more project fieldsDone
- StatusShow more project fieldsTracked for Docs Freeze
- StatusShow more project fieldsTracked for Docs Freeze
- StatusShow more project fieldsNot for release
Activity
SergeyKanzhelev commentedon May 31, 2024
Discussed with @mrunalp and we fine to add this to milestone:
/milestone v1.31
/label lead-opted-in
/stage alpha
ArkaSaha30 commentedon Jun 4, 2024
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
alphaforv1.31(correct me, if otherwise)Here's where this enhancement currently stands:
implementableforlatest-milestone: v1.31. KEPs targetingstablewill need to be marked asimplementedafter code PRs are merged and the feature gates are removed.For this KEP, we would need to update the following:
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!
jpbetz commentedon Jun 11, 2024
PRR reviewer here. Is there a KEP to review? Only a few days left till enhancements freeze..
SergeyKanzhelev commentedon Jun 12, 2024
Yes, we have polished some imlpementation details, but from PRR perspective it is very straightforward
richabanker commentedon Jun 12, 2024
Looks like this is the KEP PR: #4681
SergeyKanzhelev commentedon Jun 13, 2024
@ArkaSaha30 this KEP can be marked as done for all the checkboxes you listed. Thank you!
dipesh-rawat commentedon Jun 13, 2024
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!276 remaining items
harche commentedon Jul 27, 2026
Thanks @kernel-kun for reaching out, there is not doc update for 1.37 for this feature.
SwathiR03 commentedon Jul 29, 2026
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?
harche commentedon Jul 29, 2026
Thanks @SwathiR03 for reaching out, we don't have any blog post for this cycle for this feature.
karimzakzouk commentedon Aug 18, 2026
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 inkep.yamltoimplemented, and then close this issue?Thanks!
harche commentedon Aug 19, 2026
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.yamlstill hasstatus: implementable, notimplemented. The current stage isstage: beta, withlatest-milestone: v1.36. Thestable: v1.37value is only the target, not a completed graduation.In kubernetes/kubernetes,
ResourceHealthStatusis Alpha in 1.31 and Beta (default on) in 1.36. There is no GA orLockToDefaultentry. The same is true forResourceHealthStatusMessage.The last promotion was to beta for 1.36 (enhancements#5689, kubernetes#135255). There is no GA promotion PR.
The
stage/stablelabel on this issue means we are targeting stable this cycle, not that it already GAed. Please keep this issue open. We should not setstatus: implementedor close it until the feature actually graduates.Thanks!
karimzakzouk commentedon Aug 19, 2026
Hey @harche , you're right, my bad on the previous comment. I read the
stage/stablelabel 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-inandtracked/*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-inlabel 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
kubernetes-prow commentedon Aug 19, 2026
@karimzakzouk: Those labels are not set on the issue:
lead-opted-in, tracked/yes, tracked/noDetails
In response to this:
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.
harche commentedon Aug 19, 2026
@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:
WatchHealthStatus, v1 DRAResourceHealth gRPC, dual v1/v1alpha1 serving).If you are okay with opting this in, would you be able to add
/label lead-opted-inand/milestone v1.38? If you are also comfortable targeting GA this cycle,/stage stablewould be appreciated as well.