Hello Release Team,
I request a code freeze exception for the v1.37 release cycle.
Enhancement name: KEP-4680: Add Resource Health Status to the Pod
Status for Device Plugin and DRA
Enhancement status (alpha/beta/stable): beta
SIG: Node (WG Device Management)
k/enhancements repo issue #:
https://github.com/kubernetes/enhancements/issues/4680
PR #'s:
https://github.com/kubernetes/kubernetes/pull/139477
Additional time needed : 5 days because API reviewers' bandwidth is
limited near code freeze time.
Reason this enhancement is critical for this milestone: The PR
promotes the DRAResourceHealth kubelet gRPC API from v1alpha1 to
v1beta1, matching the feature's beta graduation in this cycle. Without
it, the beta feature ships with an alpha only API for another release.
Risks from adding code late: Low. The PR is complete, has been
reviewed and approved by Patrick and Ed, and is passing CI. The only
outstanding item is API approver sign-off for
staging/src/
k8s.io/kubelet/pkg/apis, where the v1beta1 proto is
identical to the existing v1alpha1, so there is no change in API
semantics to review. The change is internal to the kubelet and its
plugin interface rather than a REST API, and it was verified end to
end against real drivers on both the v1alpha1 and v1beta1 paths.
Risks from cutting enhancement: The PR also introduces the new
WatchHealthStatus method on the DRAPlugin helper interface, which
moves gRPC serving into the kubeletplugin helper so that future API
promotions never require driver changes again. If the PR slips to
1.38, drivers adopting health reporting in the 1.37 timeframe must
hand implement the v1alpha1 gRPC service and then migrate to the new
interface one release later. Landing it now means driver authors only
ever write against the final interface.
Thanks,
Harshal Patil