Skip to content

Blog: KEP-4680 Resource Health Status reaches Beta in v1.36#54534

Draft
harche wants to merge 1 commit intokubernetes:mainfrom
harche:blog/kep-4680-resource-health-status
Draft

Blog: KEP-4680 Resource Health Status reaches Beta in v1.36#54534
harche wants to merge 1 commit intokubernetes:mainfrom
harche:blog/kep-4680-resource-health-status

Conversation

@harche
Copy link
Contributor

@harche harche commented Feb 18, 2026

Summary

Placeholder PR for the KEP-4680 feature blog, as requested by the v1.36 Communications Team
in kubernetes/enhancements#4680 (comment).

KEP: https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/4680-add-resource-health-to-pod-status/README.md

This blog covers the Resource Health Status feature reaching Beta in v1.36,
which exposes device health information (from Device Plugin and DRA) in Pod Status.

/sig node

@k8s-ci-robot k8s-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. sig/node Categorizes an issue or PR as relevant to SIG Node. labels Feb 18, 2026
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign natalisucks for approval. For more information see the Code Review Process.

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

Details 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 area/blog Issues or PRs related to the Kubernetes Blog subproject label Feb 18, 2026
@k8s-ci-robot k8s-ci-robot added language/en Issues or PRs related to English language cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Feb 18, 2026
@lmktfy
Copy link
Member

lmktfy commented Feb 18, 2026

Hello from the blog team.

We recommend drafting in either HackMD or Google Docs; once you're happy with the text and your buddy / reviewer is happy too, you can switch back to Git / GitHub ready for it to merge in.

There's a guide to all this, well most of it, on the Kubernetes website.

Copy link
Member

Choose a reason for hiding this comment

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

Hello from the blog team.

We recommend drafting in either HackMD or Google Docs; once you're happy with the text and your buddy / reviewer is happy too, you can switch back to Git / GitHub ready for it to merge in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/blog Issues or PRs related to the Kubernetes Blog subproject cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. language/en Issues or PRs related to English language sig/node Categorizes an issue or PR as relevant to SIG Node. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Development

Successfully merging this pull request may close these issues.

3 participants