ComputeDomain v1beta1 — resource.nvidia.com

apiVersion string

APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources

kind string

Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds

metadata object

spec object

ComputeDomainSpec provides the spec for a ComputeDomain.

channel object required

ComputeDomainChannelSpec provides the spec for a channel used to run a workload inside a ComputeDomain.

allocationMode string

Allows for requesting all IMEX channels (the maximum per IMEX domain) or precisely one.

enum: All, Single

resourceClaimTemplate object required

ComputeDomainResourceClaimTemplate provides the details of the ResourceClaimTemplate to generate.

name string required

numNodes integer required

Intended number of IMEX daemons (i.e., individual compute nodes) in the ComputeDomain. Must be zero or greater. With `featureGates.IMEXDaemonsWithDNSNames=true` (the default), this is recommended to be set to zero. Workload must implement and consult its own source of truth for the number of workers online before trying to share GPU memory (and hence triggering IMEX interaction). When non-zero, `numNodes` is used only for automatically updating the global ComputeDomain `Status` (indicating `Ready` when the number of ready IMEX daemons equals `numNodes`). In this mode, a `numNodes` value greater than zero in particular does not gate the startup of IMEX daemons: individual IMEX daemons are started immediately without waiting for its peers, and any workload pod gets released right after its local IMEX daemon has started. With `featureGates.IMEXDaemonsWithDNSNames=false`, `numNodes` must be set to the expected number of worker nodes joining the ComputeDomain. In that mode, all workload pods are held back (with containers in state `ContainerCreating`) until the underlying IMEX domain has been joined by `numNodes` IMEX daemons. Pods from more than `numNodes` nodes trying to join the ComputeDomain may lead to unexpected behavior. The `numNodes` parameter is deprecated and will be removed in the next API version.

status object

Global ComputeDomain status. Can be used to guide debugging efforts. Workload however should not rely on inspecting this field at any point during its lifecycle.

nodes []object

cliqueID string required

index integer

The Index field is used to ensure a consistent IP-to-DNS name mapping across all machines within an IMEX domain. Each node's index directly determines its DNS name within a given NVLink partition (i.e. clique). In other words, the 2-tuple of (CliqueID, Index) will always be unique. This field is marked as optional (but not omitempty) in order to support downgrades and avoid an API bump.

ipAddress string required

name string required

status string

The Status field tracks the readiness of the IMEX daemon running on this node. It gets switched to Ready whenever the IMEX daemon is ready to broker GPU memory exchanges and switches to NotReady when it is not. It is marked as optional in order to support downgrades and avoid an API bump.

enum: Ready, NotReady

status string required

enum: Ready, NotReady