> This page is for Workload Identity, version Latest · v1.16.0-rc.7 (default).
> For other versions, use one of these documentation indexes:
> - Latest · v1.16.0-rc.7 (default): https://docs.nvidia.com/workload-identity/v1.16.0-rc.7/llms.txt
> - v1.16.0-rc.5: https://docs.nvidia.com/workload-identity/v1.16.0-rc.5/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.nvidia.com/workload-identity/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.nvidia.com/workload-identity/_mcp/server.

# NVIDIA Workload Identity

NVIDIA Workload Identity provides hardware-backed identities for bare-metal
hosts, [KubeVirt](https://kubevirt.io/user-guide/) VMs, Kubernetes Pods, and workloads in [Kata Containers](https://katacontainers.io/). Each
workload receives a unique identity containing its tenant, service, and resource
identity.

A workload presents a signed identity credential to a relying party, which
verifies the credential to authenticate the caller. For example, a secrets
manager can authenticate a VM's tenant identity before applying its rules for
access to a requested secret.

Identities build from the operator-owned DPU, which runs in zero trust mode. The
DPU establishes the identity of its paired bare-metal host. The attested host
provides identities to KubeVirt VMs and Kubernetes Pods. Pods running in Kata
Containers obtain their identities through a proxy that carries the host's [SPIRE](https://spiffe.io/docs/latest/spire-about/)
Workload API across the guest VM boundary.

DSX data halls run independent SPIRE deployments, each attesting local nodes and
workloads and issuing signed identity credentials called [SVIDs](https://spiffe.io/docs/latest/spiffe-about/spiffe-concepts/#spiffe-verifiable-identity-document-svid). NVIDIA Workload
Identity Keys exchanges local SPIRE JWT-SVIDs for DSX JWT-SVIDs and distributes
public signing keys through the [DSX Event Bus](https://docs.nvidia.com/dsx-exchange/architecture#dsx-event-bus), so relying parties can
authenticate workloads across data halls.

Kubernetes and DPUService Pods receive DSX JWT-SVIDs through an injected
token-fetcher sidecar. KubeVirt VMs request DSX JWT-SVIDs from DSX IMDS. Paired
bare-metal hosts use DSX JWT-SVIDs from DPU-hosted DSX IMDS to attest their SPIRE
agents. See the
[user guide](/workload-identity/user-guide/examples) for requests and verification examples.

See [Architecture](/workload-identity/architecture) for identity delivery and the
[Identity contract](/workload-identity/identity-contract) for subject formats and ownership.

## Deployment

Install the [NVIDIA Workload Identity Helm chart](/workload-identity/charts/dsx-identity)
once per identity shard. The chart README covers prerequisites, configuration,
and optional [DPF](https://github.com/NVIDIA/doca-platform) integration, including the [DSX IMDS](/workload-identity/charts/dsx-imds)
and [DPU token-fetcher admission](/workload-identity/charts/dsx-token-fetcher) child charts.

## Components

- [NVIDIA Workload Identity Controller](/workload-identity/components/identity-controller)
- [DSX IMDS Network Setup](/workload-identity/components/imds-network-setup)
- [`dsx_imds` NodeAttestor agent plugin](/workload-identity/components/node-attestor-agent)
- [`dsx_imds` NodeAttestor server plugin](/workload-identity/components/node-attestor-server)
- [`dpu_hw` NodeAttestor server plugin](https://github.com/NVIDIA/doca-platform/tree/545320feb894f20577fa0abf6885c6aafc4fb2eb/cmd/dpu-hw-server)
- [DSX Token Fetcher](/workload-identity/components/token-fetcher)
- [NVIDIA Workload Identity Keys Proxy CSI Driver](/workload-identity/components/keys-proxy-csi-driver)
- [Generate Signing Keyset](/workload-identity/components/generate-signing-keyset)
- [DSX IMDS](/workload-identity/components/imds)
- [NVIDIA Workload Identity Keys](/workload-identity/components/identity-keys)
- [Kata UDS Proxy](/workload-identity/components/kata-uds-proxy)

### SPIRE upgrades

Before upgrading SPIRE, check its
[upgrade requirements](https://github.com/spiffe/spire/blob/main/doc/upgrading.md)
for supported version skew, upgrade order, and configuration changes.