Configure an infrastructure provider: LaunchLayer
This page describes how to confirm that the NVIDIA Kubernetes Engine (NVKE) management plane can request machines from LaunchLayer, how to manage the credentials it uses, and which LaunchLayer identifiers each workload cluster request needs. NVKE requests machines through CAPLL, the Cluster API (CAPI) infrastructure provider for LaunchLayer, which runs on the management cluster and calls the LaunchLayer API with an OAuth2 client. You do this after you install the management plane and before you create the first workload cluster.
Infrastructure providers describes how NVKE uses a provider. See also Preview status and known limitations.
Before you begin
- You have installed the management plane with the
deploy/launchlayerdeploy path, as its README describes. It is the install in Install the management plane, run with--deploy-path deploy/launchlayerand the inputs the README lists. It installs CAPLL in thecapll-systemnamespace and writes thelaunchlayer-credentialsSecret from thelaunchLayersection of the stack config. - Your SPIRE server and node images support DSX IMDS node attestation, as described in Infrastructure Providers.
- You have the management cluster kubeconfig,
<CLUSTER_NAME>.kubeconfig, andkubectlonPATH. The kubeconfig must be able to read Secrets in thecapll-systemnamespace. nvkectlpoints at your management plane. With API authentication on,nvkectl get providersfails, as described in Configure an infrastructure provider: NICo; the steps give akubectlalternative.- In LaunchLayer, you have an OAuth2 client for CAPLL, a site, an organization or an existing virtual private cloud (VPC), and the instance types and host OS profiles for the nodes.
Run the commands on this page with KUBECONFIG set:
Confirm that CAPLL is running
-
Check the provider state.
The
launchlayerrow readsCONFIGURED.NOT-INSTALLEDorNOT-CONFIGUREDmeans the install did not complete; run it again as described in Run the install again.DEGRADEDmeans the CAPLL controller is not available or has no--base-url.UNKNOWNusually means the kubeconfig cannot read Secrets incapll-system. For any state other thanCONFIGURED, theDETAILcolumn names the cause.With API authentication on, check CAPLL with
kubectlinstead:The CAPLL controller Deployment shows all replicas ready, and the Secret
launchlayer-credentialsis listed. -
Check that the management plane is running.
The Deployment is ready. A node attestation method other than
dsxImdswith SPIFFE on never gets this far: the chart refuses to render, so the install fails and its output namesnodeAgent.spireAttestationMethod.
CONFIGURED does not mean the credentials work. CAPLL first uses them when it reconciles a workload cluster’s LaunchLayerCluster.
Manage the LaunchLayer credentials
CAPLL gets an OAuth2 token for the LaunchLayer API with the client in the Secret launchlayer-credentials in the capll-system namespace.
The LaunchLayer API address is not in the Secret. It is the CAPLL --base-url flag, from launchLayer.baseURL in the stack config.
To rotate the client secret or change any other value, update the stack config or NVKECTL_LAUNCHLAYER_CLIENT_SECRET, then run the install again. The install writes the Secret from those inputs.
Collect the LaunchLayer identifiers
Each workload cluster request carries its LaunchLayer identifiers in a launchLayer object on the cluster, the control plane and each node pool, in place of nico. Every field is fixed at creation.
vmProfile takes the place of hostOSProfile for virtual machines. With SPIFFE on and nodeAgent.externalMTLS.enabled off, the API rejects it, because DSX IMDS attests bare-metal machines only.
In the cluster spec from Create a workload cluster, replace each nico object with a launchLayer object:
Replace the placeholders with the values in the table above. The other fields of the spec are the same as for NICo.
Verify
-
Check the provider state.
The
launchlayerrow readsCONFIGURED. With API authentication on, runkubectl -n capll-system get deploy,secretinstead. -
Check that the Secret has its keys.
The
Datasection listsclientID,clientSecretandissuerURLwith a non-zero size, andscopes. The command does not print the values.
Check a workload cluster’s LaunchLayer resources
After you create a cluster, NVKE creates a LaunchLayerCluster named after the workload cluster and a LaunchLayerMachine for each node, named after the node, in the nvke-system namespace.
-
Check the cluster.
The
VPCReadycondition isTrue, and so isSecurityGroupsReadywhen the cluster declares security groups. The reasonWaitingForEndpointConfigmeans CAPLL cannot read thelaunchlayer-credentialsSecret or has no--base-url. -
Check the machines.
For a machine that does not come up,
kubectl -n nvke-system describe launchlayermachine <NODE_NAME>shows why in itsMachineProvisionedcondition.
Next steps
- Secure the NVKE API.
- Create a workload cluster with the LaunchLayer identifiers you collected.