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

[SergeyKanzhelev]

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
• Alpha2 (DRA support)
  • KEP (k/enhancements) update PR(s):
    • 1.32 updates to device failures for alpha2 #4862
    • 1.33 bump the release for Add Resource Health Status to the Pod Status for Device Plugin and DRA #5150
    • 1.34 KEP-4680 is targeting alpha for DRA in 1.34 #5410, KEP 4680: Update README.md for DRA #5302
  • Code (k/k) update PR(s):
    • 1.32 Update Device Health fields description for KEP-4680 kubernetes#128299
    • 1.33 ?
    • 1.34 Expose DRA device health in PodStatus kubernetes#130606
  • Docs (k/website) update PR(s):
    • docs(DRA): Document device health monitoring in PodStatus website#51731
    • Blog with DRA updates in 1.34 website#51488
• Beta
  • KEP (k/enhancements) update PR(s):
    • Promote 4680 to beta #5642
    • KEP-4680: promote to beta (v1.36) #5689
  • 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

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

[SergeyKanzhelev]

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

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

[ArkaSaha30]

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!

[jpbetz]

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

[SergeyKanzhelev]

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

[richabanker]

Looks like this is the KEP PR: #4681

[SergeyKanzhelev]

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

[dipesh-rawat]

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!