Infrastructure providers
An infrastructure provider supplies the machines that NVIDIA Kubernetes Engine (NVKE) turns into workload cluster nodes. NVKE supports two: NVIDIA Infra Controller (NICo), through CAPNICo, and LaunchLayer, through CAPLL. Both are Cluster API (CAPI) infrastructure providers that run on the management cluster.
How a workload cluster gets its machines
The diagram shows what happens when you create a workload cluster. The NVKE management plane and CAPNICo or CAPLL run on the management cluster. The table after the diagram explains each numbered step.
Supported providers
How a deployment selects a provider
You select the provider when you install the management plane, by choosing the deploy path: deploy/nico for NICo or deploy/launchlayer for LaunchLayer. Each deploy path installs its provider, writes its credentials Secret and sets the controller chart values the provider needs.
The controller chart value supportedInfraProviders lists the provider objects the NVKE API accepts. The API rejects a request that carries any other provider object with 400. The node attestation method applies to every new node of a deployment. With SPIFFE on, LaunchLayer requires DSX IMDS, so a deployment whose NICo nodes attest with TPM cannot also accept launchLayer.
The provider set is closed
supportedInfraProviders accepts only nico, launchLayer and infra. With any other value, the controller chart fails to render and the controller does not start. infra accepts raw Cluster API manifests from the caller and is not an infrastructure provider in its own right.
Adding a provider is a change to NVKE, not configuration. It needs a Cluster API infrastructure provider for the platform and, in the dsx-ai-factory/nvke repository:
- A provider object in the REST API,
controller/api/openapi.yaml. - A provider client under
controller/internal/clients/that implementsProviderClient. - The provider name in the
supportedInfraProviderschecks of the controller chart and the controller configuration. - RBAC in the controller chart for the provider’s custom resource definitions (CRDs).
- An entry in
nvkectl get providers, incli/internal/providers. - A deploy path under
deploy/that installs the provider.
To propose a provider, open an issue in the dsx-ai-factory/nvke repository.
Check providers and their clusters
nvkectl get providers lists each provider with its state, read from the management cluster. CONFIGURED means the provider’s CRDs are established, its controller is available and its credentials Secret exists. The provider pages describe the other states.
To see which provider each workload cluster uses, list the Cluster API clusters with their infrastructure kind:
PROVIDER reads NicoCluster or LaunchLayerCluster. Each provider page shows how to read that cluster’s provider objects.
Next steps
- Install the management plane with the deploy path for your provider.
- Configure an infrastructure provider: NICo or Configure an infrastructure provider: LaunchLayer.