Skip to content

Conversation

@Jpsassine
Copy link
Contributor

@Jpsassine Jpsassine commented Jul 8, 2025

Description

Add a new blog post about the new functionality expansion of KEP-4680 which now covers DRA in 1.34. The blog post explains context and the nature of the feature for DRA.

Issue

KEP: kubernetes/enhancements#4680

Closes: #

@k8s-ci-robot k8s-ci-robot added this to the 1.34 milestone Jul 8, 2025
@k8s-ci-robot k8s-ci-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 8, 2025
@netlify
Copy link

netlify bot commented Jul 8, 2025

👷 Deploy Preview for kubernetes-io-vnext-staging processing.

Name Link
🔨 Latest commit 0d8dae7
🔍 Latest deploy log https://app.netlify.com/projects/kubernetes-io-vnext-staging/deploys/68a90504c842f00008f8376d

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Jul 8, 2025
@k8s-ci-robot
Copy link
Contributor

Welcome @Jpsassine!

It looks like this is your first PR to kubernetes/website 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/website has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

@k8s-ci-robot k8s-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Jul 8, 2025
@netlify
Copy link

netlify bot commented Jul 8, 2025

Pull request preview available for checking

Built without sensitive environment variables

Name Link
🔨 Latest commit 0d8dae7
🔍 Latest deploy log https://app.netlify.com/projects/kubernetes-io-main-staging/deploys/68a905040aff2700082256ae
😎 Deploy Preview https://deploy-preview-51556--kubernetes-io-main-staging.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@Jpsassine Jpsassine changed the title test: Initial commit for draft PR KEP-4860: Blog Placeholder Jul 11, 2025
@aibarbetta
Copy link
Member

Hi @Jpsassine, did you mean to open this for kubernetes/enhancements#4680?
@mortent will cover all DRA KEPs in blog #51488. Please let me know if you plan to write a separate blog, or join the one linked.

@Jpsassine
Copy link
Contributor Author

@aibarbetta, after speaking with @SergeyKanzhelev we see value in having an independent blog post for this specific DRA feature as well as having it included in the main DRA blog post written by @mortent. What exactly is the deadline for this? I had made this placeholder just in case.

@aibarbetta
Copy link
Member

/retitle [WIP] Add v1.34 Blog Post for Resource Health Status in Pod Status for Device Plugin and DRA KEP-4680

@k8s-ci-robot k8s-ci-robot changed the title KEP-4860: Blog Placeholder [WIP] Add v1.34 Blog Post for Resource Health Status in Pod Status for Device Plugin and DRA KEP-4680 Jul 15, 2025
@aibarbetta
Copy link
Member

@aibarbetta, after speaking with @SergeyKanzhelev we see value in having an independent blog post for this specific DRA feature as well as having it included in the main DRA blog post written by @mortent. What exactly is the deadline for this? I had made this placeholder just in case.

Hi @Jpsassine @SergeyKanzhelev, this PR should have front matter and blog content ready to review by Friday 8th August 2025

@aibarbetta
Copy link
Member

/sig release
/area blog

@k8s-ci-robot k8s-ci-robot added sig/release Categorizes an issue or PR as relevant to SIG Release. area/blog Issues or PRs related to the Kubernetes Blog subproject labels Jul 15, 2025
@k8s-ci-robot k8s-ci-robot added area/localization General issues or PRs related to localization area/release-eng Issues or PRs related to the Release Engineering subproject area/web-development Issues or PRs related to the kubernetes.io's infrastructure, design, or build processes needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. language/bn Issues or PRs related to Bengali language language/en Issues or PRs related to English language language/hi Issues or PRs related to Hindi language language/ja Issues or PRs related to Japanese language language/ko Issues or PRs related to Korean language language/pl Issues or PRs related to Polish language language/pt Issues or PRs related to Portuguese language language/ru Issues or PRs related to Russian language language/uk Issues or PRs related to Ukrainian language language/vi Issues or PRs related to Vietnamese language labels Jul 29, 2025
@SergeyKanzhelev
Copy link
Member

I would publish the general DRA blog first, ideally with a comment in the section that covers KEP-4680 saying a dedicated blog for this feature is coming. But I'm open to suggestions 👀

If there are general DRA blog where this can be integrated into, it will be also OK. I just worry that general DRA blog that also recommend to onboard to thus alpha feature may not be understood correctly. Making separate messages "DRA is GA" and "use new Alpha features for DRA" may be easier to digest

@Jpsassine Jpsassine force-pushed the dev-1.34 branch 2 times, most recently from 7834e4e to 56a57a6 Compare August 11, 2025 21:04
Copy link
Member

@lmktfy lmktfy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks.

Make sure to mark this as draft in the front matter (the PR should not be marked as draft, though). Release Comms will assign a publication date and un-draft it in a follow up PR.

Copy link
Member

@SergeyKanzhelev SergeyKanzhelev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Aug 14, 2025
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: e207d5a6ed71250c7a534de97bf0f7a7d1c378bb

@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Aug 14, 2025
@Jpsassine
Copy link
Contributor Author

@lmktfy is this still on track for release, or is there something I need to do still? Just want to make sure, thanks.

@aibarbetta
Copy link
Member

@lmktfy is this still on track for release, or is there something I need to do still? Just want to make sure, thanks.

Hi @Jpsassine yes, this is still being tracked as a v1.34 post-release communication

This commit adds the feature blog post for the v1.34 release, covering the extension of device health monitoring to Dynamic Resource Allocation (DRA).

This feature thats  part of KEP-4680, allows DRA plugins to report device health directly in the Pod's status, improving observability for workloads using specialized hardware.

Refs: https://github.com/kubernetes/enhancements/issues/i4680
Copy link
Contributor

@graz-dev graz-dev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

with one comment


The rise of AI/ML and other high-performance workloads has made specialized hardware like GPUs, TPUs, and FPGAs a critical component of many Kubernetes clusters. However, as discussed in a [previous blog post about navigating failures in Pods with devices](/blog/2025/07/03/navigating-failures-in-pods-with-devices/), when this hardware fails, it can be difficult to diagnose, leading to significant downtime. With the release of Kubernetes v1.34, we are excited to announce a new alpha feature that brings much-needed visibility into the health of these devices.

This work extends the functionality of [KEP-4680](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/4680-add-resource-health-to-pod-status), which first introduced a mechanism for reporting the health of devices managed by Device Plugins. Now, this capability is being extended to *Dynamic Resource Allocation (DRA)*. Controlled by the `ResourceHealthStatus` feature gate, this enhancement allows DRA drivers to report device health directly into a Pod's `.status` field, providing crucial insights for operators and developers.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
This work extends the functionality of [KEP-4680](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/4680-add-resource-health-to-pod-status), which first introduced a mechanism for reporting the health of devices managed by Device Plugins. Now, this capability is being extended to *Dynamic Resource Allocation (DRA)*. Controlled by the `ResourceHealthStatus` feature gate, this enhancement allows DRA drivers to report device health directly into a Pod's `.status` field, providing crucial insights for operators and developers.
This work extends the functionality of [KEP-4680](kep.k8s.io/4680), which first introduced a mechanism for reporting the health of devices managed by Device Plugins. Now, this capability is being extended to *Dynamic Resource Allocation (DRA)*. Controlled by the `ResourceHealthStatus` feature gate, this enhancement allows DRA drivers to report device health directly into a Pod's `.status` field, providing crucial insights for operators and developers.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@graz-dev I think that suggestion isn't quite right

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Aug 23, 2025
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: f05f7d88b93c63aed0bda1e79f088343060cc9a6

@lmktfy
Copy link
Member

lmktfy commented Aug 23, 2025

/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lmktfy, SergeyKanzhelev

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 23, 2025
@k8s-ci-robot k8s-ci-robot merged commit 394208d into kubernetes:main Aug 23, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. area/blog Issues or PRs related to the Kubernetes Blog subproject cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. language/en Issues or PRs related to English language lgtm "Looks good to me", indicates that a PR is ready to be merged. sig/docs Categorizes an issue or PR as relevant to SIG Docs. sig/release Categorizes an issue or PR as relevant to SIG Release. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants