Architecture
Hardware-backed workload identity starts at the operator-owned DPU, which runs
in zero trust mode. The DPU anchors attestation for its paired bare-metal host.
The attested host provides identities to its Pods and VMs. The dpu_hw
NodeAttestor identifies each DPU by its serial number. The bundled dpu_hw
server accepts the serial as plaintext attestation data.
SPIRE runs a server that registers identities and agents that identify local callers. Node attestation verifies an agent’s attestation data before SPIRE issues its identity credential, called an SVID. Workload attestation matches caller properties to registration entries before an agent serves a workload SVID. A registration’s parent agent determines which agent can serve that identity.
An identity shard contains independent SPIRE and Identity Keys deployments.
Common Services owns the identity shard for Common Services and Data Hall
control-plane resources. Each Data Hall owns the shard for its capacity
resources. Both shards derive entries from their local DPU and LaunchLayer
source CRs, and their Pods register beneath local dsx_imds agents.
SPIRE registration parentage follows the attested agent. Resource subjects and tenant claims identify ownership. DPUs run as Kubernetes workers in their Kamaji clusters.
Every host-cluster Kubernetes worker is an operator-owned bare-metal host.
Pods on these workers use the configured operator tenant and a /bm/<node-name>/pod/<pod-uid>
subject. A tenant-facing bare-metal host is standalone and never becomes a
Kubernetes node. A KubeVirt VM runs in an operator-owned virt-launcher Pod, so
the Pod keeps its operator identity while its metadata sidecar selects the
dynamically tenant-supplied VM SVID from the same operator host Workload API.
Registration parentage
The NVIDIA Workload Identity Controller owns DPU-derived, standalone host, and
VM ClusterStaticEntry CRs. The SPIRE controller-manager registers those
entries and registers Pods directly from the chart-owned ClusterSPIFFEID
template.
Hexagons show inputs, stadiums show attested parent agent IDs, and rectangles
show static CRs or Pod registration entries. {service} comes from
global.dsx.defaultServiceName for static CRs and the
spiffe.nvidia.com/service label for Pods.
The DPU resource supplies the worker-to-DPU relationship. Its IMDS registration
allows DPU-hosted DSX IMDS to obtain the paired worker’s SPIRE JWT-SVID and
exchange it for the DSX JWT-SVID returned through link-local IMDS. The worker uses
that DSX JWT-SVID to attest its local SPIRE agent through dsx_imds.
For a tenant-assigned host, the BareMetalInstance supplies the host-to-DPU
relationship. Its entry replaces the operator fallback derived from the DPU
resource.
Local consumers exchange local SPIRE JWT-SVIDs with their shard’s NVIDIA Workload Identity Keys for DSX JWT-SVIDs. NVIDIA Workload Identity Keys instances share only public signing keys across shards.
A SPIRE JWT-SVID is a cluster-local credential obtained from the local SPIRE Workload API. A DSX JWT-SVID is the credential returned by the local NVIDIA Workload Identity Keys. SPIRE JWT-SVIDs never establish trust between shards.
Install the identity chart once per shard. Each regular management cluster that owns DPU or LaunchLayer source CRs runs the Identity Controller for its shard. Every NVIDIA Workload Identity Keys instance validates only local SPIRE JWT-SVIDs through its node-local Workload API. It serves aggregate public keys received through the Event Bus when NATS is enabled, or only local public keys when NATS is disabled.
The Event Bus, OAuth2 provider, and relying parties are external to the identity chart.
DPF registers DPU Agent and DPUService workload identities through the external DPF identity configuration. The Identity Controller registers the paired host identity served by DPU IMDS.