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): @SergeyKanzhelev
• 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.33
  • Beta release target (x.y): 1.34
  • Stable release target (x.y): 1.34

• 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

  • 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
  • Code (k/k) update PR(s):
    • 1.32 Update Device Health fields description for KEP-4680 kubernetes#128299
    • 1.33 ?
  • Docs (k/website) update PR(s):
    • KEP-4680: placeholder for website updates website#48544
    • DRA pod status (KEP 4680) website#48547

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!

[rashansmith]

Hi @SergeyKanzhelev,

👋 from the v1.31 Communications Team! We'd love for you to opt in to write a feature blog about your enhancement!
Some reasons why you might want to write a blog for this feature include (but are not limited to) if this introduces breaking changes, is important to our users, or has been in progress for a long time and is graduating.

To opt in, let us know and open a Feature Blog placeholder PR against the website repository by 3rd July, 2024. For more information about writing a blog see the blog contribution guidelines.

Note: In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.

[Princesso]

Hi @SergeyKanzhelev, gentle reminder to raise a draft doc PR against dev-1.31 for this enhancement, before Thursday, June 27, 2024, 18:00 PDT.

[rashansmith]

Hey @SergeyKanzhelev, friendly reminder about the upcoming blog opt-in and placeholder deadline on July 3rd. Please open a blog placeholder PR if you are interested in contributing a blog.

[SergeyKanzhelev]

Hey @SergeyKanzhelev, friendly reminder about the upcoming blog opt-in and placeholder deadline on July 3rd. Please open a blog placeholder PR if you are interested in contributing a blog.

Done, thanks for reminder! kubernetes/website#47029

[rashansmith]

Hello @SergeyKanzhelev,

Hey @SergeyKanzhelev, friendly reminder about the upcoming blog opt-in and placeholder deadline on July 3rd. Please open a blog placeholder PR if you are interested in contributing a blog.

Done, thanks for reminder! kubernetes/website#47029

Hey @SergeyKanzhelev, friendly reminder about the upcoming blog opt-in and placeholder deadline on July 3rd. Please open a blog placeholder PR if you are interested in contributing a blog.

Done, thanks for reminder! kubernetes/website#47029

Hey @SergeyKanzhelev, you currently have a PR for a docs change. To submit a blog post placeholder, create a PR on The website blogpost directory. Here is an example PR. Let me know if you have any questions!

[ArkaSaha30]

Hey again @SergeyKanzhelev 👋, Enhancements team here,

Just checking in as we approach code freeze at 02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 2024.

Here's where this enhancement currently stands:

• All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• All PR/s are ready to be merged (they have approved and lgtm labels applied) by the code freeze deadline. This includes tests.

Regarding this enhancement, it appears that there are currently no open pull requests in the k/k repository related to it.

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

• Ensure all PRs to the Kubernetes repo related to your enhancement are linked in the above issue description (for tracking purposes).
• Ensure all PRs are prepared for merging (they have approved and lgtm labels applied) by the code freeze deadline. This includes tests.

If you anticipate missing code freeze, you can file an exception request in advance.

The status of this enhancement is marked as at risk for code freeze.

[ArkaSaha30]

Hey again @SergeyKanzhelev 👋, 1.31 Enhancements team here,

Just a quick friendly reminder as we approach code freeze in about 2 days, at 02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 2024.

The current status of this enhancement is marked as at risk for code freeze. A few requirements mentioned in the comment #4680 (comment) still need to be completed. The following PR as per the description still needs to be merged:

• Implement resource health in pod status (KEP 4680) kubernetes#126243

If you anticipate missing code freeze, you can file an exception request in advance.

[SergeyKanzhelev]

Note for self to add to the beta graduation requirements: kubernetes/kubernetes#126243 (comment)

Potential code change to improve stress behavior: https://github.com/kubernetes/kubernetes/pull/126243/files#r1688457694

[kannon92]

/stage alpha

[SergeyKanzhelev]

@lzung all requirements are satisfied now

[lzung]

Hello @SergeyKanzhelev 👋,

Now that PR #5150 has been merged, all the KEP requirements are in place for alpha release and merged into k/enhancements. This enhancement is all good for the upcoming enhancements freeze. 🚀

The status of this enhancement is now marked as tracked for enhancement freeze. Thank you!

[sreeram-venkitesh]

Hi @SergeyKanzhelev! 👋 v1.33 Docs Shadow here.

Does this enhancement work planned for v1.33 require any new docs or modification to existing docs?

If so, please follow the steps here to open a PR against dev-1.33 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday 27th February 2025 18:00 PDT.

Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.

Thank you!

[dshebib]

@sreeram-venkitesh This is just a feature bump and does not require any new documentation. The docs were merged previously here: kubernetes/website#47029

[rytswd]

Hi @SergeyKanzhelev 👋 -- this is Ryota (@rytswd) from the 1.33 Communications Team!

For the 1.33 release, we are currently in the process of collecting and curating a list of potential feature blogs, and we'd love for you to consider writing one for your enhancement!

As you may be aware, feature blogs are a great way to communicate to users about features which fall into (but not limited to) the following categories:

• This introduces some breaking change(s)
• This has significant impacts and/or implications to users
• ...Or this is a long-awaited feature, which would go a long way to cover the journey more in detail 🎉

To opt in to write a feature blog, could you please let us know and open a "Feature Blog placeholder PR" (which can be only a skeleton at first) against the website repository by Wednesday, 5th March, 2025? For more information about writing a blog, please find the blog contribution guidelines 📚

Tip

Some timeline to keep in mind:

• 02:00 UTC Wednesday, 5th March, 2025: Feature blog PR freeze
• Monday, 7th April, 2025: Feature blogs ready for review
• You can find more in the release document

Note

In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.

[lzung]

Hey again @SergeyKanzhelev 👋, 1.33 Enhancements team here,

Just checking in as we approach code freeze at at 2:00 UTC Friday 21st March 2025 / 19:00 PDT Thursday 20th March 2025.

Here's where this enhancement currently stands:

• All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• All PR/s are ready to be merged (they have approved and lgtm labels applied) by the code freeze deadline. This includes tests.

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

• Ensure all PRs to the Kubernetes repo related to your enhancement are linked in the above issue description (for tracking purposes).
• Ensure all PRs are prepared for merging (they have approved and lgtm labels applied) by the code freeze deadline. This includes tests.

If you anticipate missing code freeze, you can file an exception request in advance.

The status of this enhancement is marked as at risk for code freeze.

[rytswd]

Hi @SergeyKanzhelev 👋, 1.33 Communications Team here again!

This is a gentle reminder for the feature blog deadline mentioned above, which is 02:00 UTC Wednesday, 5th March, 2025. To opt in, please let us know and open a Feature Blog placeholder PR against k/website by the deadline. If you have any questions, please feel free to reach out to us!

Tip

Some timeline to keep in mind:

• 02:00 UTC Wednesday, 5th March, 2025: Feature blog PR freeze
• Monday, 7th April, 2025: Feature blogs ready for review
• You can find more in the release document

Note

In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.

[dipesh-rawat]

Hi @lzung 👋, v1.33 Enhancements team here,

Just a quick friendly reminder as we approach the code freeze later this week, at 02:00 UTC Friday 21st March 2025 / 19:00 PDT Thursday 20th March 2025.

The current status of this enhancement is marked as At risk for code freeze. There are a few requirements mentioned in the comment #4680 (comment) that still need to be completed.

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

[dipesh-rawat]

Hello @SergeyKanzhelev 👋, v1.33 Enhancements team here,

Unfortunately, the implementation (code-related) PRs associated with this enhancement are not in the merge-ready state by code-freeze and hence this enhancement is now removed from the v1.33 milestone.

If you still wish to progress this enhancement in v1.33, please file an exception request as soon as possible, within three days. If you have any questions, you can reach out in the #release-enhancements channel on Slack and we'll be happy to help. Thanks!

/milestone clear

[ArangoGutierrez]

/cc

[reemmadkour]

Hi, @SergeyKanzhelev @dipesh-rawat What is the status of this feature? I see it referenced under a feature gate in the Kubernetes docs but I want to confirm that it is usable since it seems from this thread it was never released? Thanks!

[jenshu]

Hi @SergeyKanzhelev 👋, 1.34 Enhancements Lead here.

I am closing the v1.33 milestone now.

If you'd like to work on this enhancement in v1.34, please have the SIG lead opt-in by adding the lead-opted-in label, which ensures it gets added to the tracking board. Also, please set the milestone to v1.34 using /milestone v1.34.

Thanks!

/remove-label lead-opted-in