6.4.2. Monitoring AllocationClaims
Procedure
Inspect active
AllocationClaimresources by running the following command:$ oc get allocationclaims -n das-operatorExample output
NAME AGE 13950288-57df-4ab5-82bc-6138f646633e-harpatil000034jma-qh5fm-worker-f-57md9-cuda-vectoradd-0 5m ce997b60-a0b8-4ea4-9107-cf59b425d049-harpatil000034jma-qh5fm-worker-f-fl4wg-cuda-vectoradd-0 5mView detailed information about a specific
AllocationClaimby running the following command:$ oc get allocationclaims -n das-operator -o yamlExample output (truncated)
apiVersion: inference.redhat.com/v1alpha1 kind: AllocationClaim metadata: name: 13950288-57df-4ab5-82bc-6138f646633e-harpatil000034jma-qh5fm-worker-f-57md9-cuda-vectoradd-0 namespace: das-operator spec: gpuUUID: GPU-9003fd9c-1ad1-c935-d8cd-d1ae69ef17c0 migPlacement: size: 1 start: 0 nodename: harpatil000034jma-qh5fm-worker-f-57md9 podRef: kind: Pod name: cuda-vectoradd-f4b84b678-l2m69 namespace: default uid: 13950288-57df-4ab5-82bc-6138f646633e profile: 1g.5gb status: conditions: - lastTransitionTime: "2025-08-06T19:28:48Z" message: Allocation is inUse reason: inUse status: "True" type: State state: inUseCheck for claims in different states by running the following command:
$ oc get allocationclaims -n das-operator -o jsonpath='{range .items[*]}{.metadata.name}{"\t"}{.status.state}{"\n"}{end}'Example output
13950288-57df-4ab5-82bc-6138f646633e-harpatil000034jma-qh5fm-worker-f-57md9-cuda-vectoradd-0 inUse ce997b60-a0b8-4ea4-9107-cf59b425d049-harpatil000034jma-qh5fm-worker-f-fl4wg-cuda-vectoradd-0 inUseView events related to
AllocationClaimresources by running the following command:$ oc get events -n das-operator --field-selector involvedObject.kind=AllocationClaimCheck
NodeAcceleratorresources to verify GPU hardware detection by running the following command:$ oc get nodeaccelerator -n das-operatorExample output
NAME AGE harpatil000034jma-qh5fm-worker-f-57md9 96m harpatil000034jma-qh5fm-worker-f-fl4wg 96mThe
NodeAcceleratorresources represent the GPU-capable nodes detected by the DAS Operator.
Additional information
The AllocationClaim custom resource tracks the following information:
- GPU UUID
- The unique identifier of the GPU device.
- Slice position
- The position of the MIG slice on the GPU.
- Pod reference
- The pod that requested the GPU slice.
- State
-
The current state of the claim (
staged,created, orreleased).
Claims start in the staged state and transition to created when all requests are satisfied. When a pod is deleted, the associated claim is automatically cleaned up.