From c9825b8d2798d095fc2b2a22af102adbfb0202ed Mon Sep 17 00:00:00 2001 From: Nitish Bhat Date: Wed, 29 Oct 2025 17:48:55 +0000 Subject: [PATCH] kubeletplugin: clarify DRAPlugin comment about driver-specific claims Clarify that PrepareResourceClaims is called with only the claims handled by this DRA driver, not all claims needed by the pod. Signed-off-by: Nitish Bhat --- .../dynamic-resource-allocation/kubeletplugin/draplugin.go | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/staging/src/k8s.io/dynamic-resource-allocation/kubeletplugin/draplugin.go b/staging/src/k8s.io/dynamic-resource-allocation/kubeletplugin/draplugin.go index efb0755472c..a8e03521635 100644 --- a/staging/src/k8s.io/dynamic-resource-allocation/kubeletplugin/draplugin.go +++ b/staging/src/k8s.io/dynamic-resource-allocation/kubeletplugin/draplugin.go @@ -58,8 +58,8 @@ type DRAPlugin interface { // for the given ResourceClaims. This is used to implement // the gRPC NodePrepareResources call. // - // It gets called with the complete list of claims that are needed - // by some pod. In contrast to the gRPC call, the helper has + // It gets called with the complete list of claims handled by this DRA driver + // that are needed by some pod. In contrast to the gRPC call, the helper has // already retrieved the actual ResourceClaim objects. // // In addition to that, the helper also: