Prerequisites
Code of Conduct
Feature Summary
Make the lifecycle-manager's default gpu-allocatable node readiness criterion recognize GPU nodes on GPU Operator GPUCluster (DRA) clusters, so ValidationRequests proceed there without a per-cluster override of the ValidationConfiguration.
Problem/Use Case
The default gpu-allocatable criterion requires nvidia.com/gpu in node.status.allocatable with a count above zero. In GPU Operator 26.7's GPUCluster mode there is no device plugin, GPUs are exposed through DRA ResourceSlices, and that resource is always zero. Every ValidationRequest, including the automatic new-node validation, stays Pending forever with Node not ready, waiting criterion=gpu-allocatable, and no dcgm-diag-test Job is created.
Proposed Solution
The readiness CEL only sees the node object, update the CEL expression to check for resourceSlice presence to confirm the GPU availability
Component
Health Monitor
Prerequisites
Code of Conduct
Feature Summary
Make the lifecycle-manager's default gpu-allocatable node readiness criterion recognize GPU nodes on GPU Operator GPUCluster (DRA) clusters, so ValidationRequests proceed there without a per-cluster override of the ValidationConfiguration.
Problem/Use Case
The default gpu-allocatable criterion requires nvidia.com/gpu in node.status.allocatable with a count above zero. In GPU Operator 26.7's GPUCluster mode there is no device plugin, GPUs are exposed through DRA ResourceSlices, and that resource is always zero. Every ValidationRequest, including the automatic new-node validation, stays Pending forever with Node not ready, waiting criterion=gpu-allocatable, and no dcgm-diag-test Job is created.
Proposed Solution
The readiness CEL only sees the node object, update the CEL expression to check for resourceSlice presence to confirm the GPU availability
Component
Health Monitor