NVIDIA Workload Identity user guide
- Kubernetes and DPUService Pods use the token-fetcher sidecar.
- Paired bare-metal hosts and KubeVirt VMs use DSX IMDS.
- Relying parties validate DSX JWT-SVIDs with the NVIDIA Workload Identity Keys JWKS endpoint.
Acquire a token from DSX IMDS
Paired bare-metal hosts reach DPU-hosted DSX IMDS through NICo. The host
dsx_imds NodeAttestor uses the returned host token to attest its SPIRE agent.
KubeVirt VMs reach a DSX IMDS sidecar in the virt-launcher Pod and receive their
VM identity. The VM network setup sidecar enables IPv4, IPv6, or both from the
primary OVN allocation. See
VM network requirements.
Request a token over IPv4:
For a VM with IPv6, use the same request with the IPv6 endpoint:
Example response:
Plain-text request:
Plain-text response:
The bare-metal host path is a node-attestation contract, not a generic host-process identity contract. See the DSX IMDS API for the versioned endpoint and plain-text response option.
Consume a DSX JWT-SVID
Use the returned token value as the relying party bearer credential:
Do not log or persist the token.
Validate a DSX JWT-SVID
Example request:
Example response:
Example verifier settings:
With NATS enabled, every shard serves the aggregate JWKS. With NATS disabled, use the issuing shard’s endpoint.