AllocationResult contains attributes of an allocated resource.
BasicDevice defines one device instance.
CELDeviceSelector contains a CEL expression for selecting a device.
Device represents one individual hardware instance that can be selected based on its attributes. Besides the name, exactly one field must be set.
DeviceAllocationConfiguration gets embedded in an AllocationResult.
DeviceAllocationResult is the result of allocating devices.
DeviceAttribute must have exactly one field set.
DeviceClaim defines how to request devices with a ResourceClaim.
DeviceClaimConfiguration is used for configuration parameters in DeviceClaim.
DeviceClass is a vendor- or admin-provided resource that contains device configuration and selectors. It can be referenced in the device requests of a claim to apply these presets. Cluster scoped.
DeviceClassConfiguration is used in DeviceClass.
DeviceClassSpec is used in a [DeviceClass] to define what can be allocated and how to configure it.
DeviceConstraint must have exactly one field set besides Requests.
DeviceRequest is a request for devices required for a claim. This is typically a request for a single resource like a device, but can also ask for several identical devices.
DeviceRequestAllocationResult contains the allocation result for one request.
DeviceSelector must have exactly one field set.
OpaqueDeviceConfiguration contains configuration parameters for a driver in a format defined by the driver vendor.
PodSchedulingContext objects hold information that is needed to schedule a Pod with ResourceClaims that use “WaitForFirstConsumer” allocation mode.
PodSchedulingContextSpec describes where resources for the Pod are needed.
PodSchedulingContextStatus describes where resources for the Pod can be allocated.
ResourceClaim describes a request for access to resources in the cluster, for use by workloads. For example, if a workload needs an accelerator device with specific properties, this is how that request is expressed. The status stanza tracks whether this claim has been satisfied and what specific resources have been allocated.
ResourceClaimConsumerReference contains enough information to let you locate the consumer of a ResourceClaim. The user must be a resource in the same namespace as the ResourceClaim.
ResourceClaimSchedulingStatus contains information about one particular ResourceClaim with “WaitForFirstConsumer” allocation mode.
ResourceClaimSpec defines what is being requested in a ResourceClaim and how to configure it.
ResourceClaimStatus tracks whether the resource has been allocated and what the result of that was.
ResourceClaimTemplate is used to produce ResourceClaim objects.
ResourceClaimTemplateSpec contains the metadata and fields for a ResourceClaim.
ResourcePool describes the pool that ResourceSlices belong to.
ResourceSlice represents one or more resources in a pool of similar resources, managed by a common driver. A pool may span more than one ResourceSlice, and exactly how many ResourceSlices comprise a pool is determined by the driver.
ResourceSliceSpec contains the information published by the driver in one ResourceSlice.