AllowMultipleAllocations marks whether the device is allowed to be allocated to multiple DeviceRequests.
If AllowMultipleAllocations is set to true, the device can be allocated more than once, and all of its capacity is consumable, regardless of whether the requestPolicy is defined or not.
ConsumesCounters defines a list of references to sharedCounters and the set of counters that the device will consume from those counter sets.
There can only be a single entry per counterSet.
The total number of device counter consumption entries must be <= 32.
In addition, the total number in the entire ResourceSlice must be <= 1024 (for example, 64 devices with 16 counters each).
BindsToNode indicates if the usage of an allocation involving this device has to be limited to exactly the node that was chosen when allocating the claim.
If set to true, the scheduler will set the ResourceClaim.Status.Allocation.NodeSelector to match the node where the allocation was made.
This is an alpha field and requires enabling the DRADeviceBindingConditions and DRAResourceClaimDeviceStatus feature gates.
BindingConditions defines the conditions for proceeding with binding.
All of these conditions must be set in the per-device status conditions with a value of True to proceed with binding the pod to the node while scheduling the pod.
The maximum number of binding conditions is 4.
The conditions must be a valid condition type string.
This is an alpha field and requires enabling the DRADeviceBindingConditions and DRAResourceClaimDeviceStatus feature gates.
Device represents one individual hardware instance that can be selected based on its attributes.