NVIDIA Workload Identity
NVIDIA Workload Identity turns shard-local SPIRE identities into DSX JWTs that relying parties can validate across shards. An identity shard contains an independent SPIRE deployment and a co-located NVIDIA Workload Identity Keys deployment. NVIDIA Workload Identity Keys validates only its local SPIRE JWT-SVIDs, issues DSX JWTs, and distributes its public signing keys through the external DSX Event Bus.
There is no SPIRE federation between shards. Cross-shard trust starts after token exchange, when another shard or relying party validates a DSX JWT with the aggregate public keys served by any NVIDIA Workload Identity Keys instance.
User guide
See the examples user guide to acquire and consume DSX JWTs through token-fetcher injection or the DSX IMDS endpoint.
Component commands and runtime configuration:
- NVIDIA Workload Identity Controller
- DSX IMDS Network Setup
dsx_imdsNodeAttestor agent plugindsx_imdsNodeAttestor server plugindpu_hwNodeAttestor server plugin- DSX Token Fetcher
- NVIDIA Workload Identity Keys Proxy CSI Driver
- Generate Signing Keyset
- DSX IMDS
- NVIDIA Workload Identity Keys
- Kata UDS Proxy
SPIRE upgrades
Before upgrading SPIRE, check its upgrade requirements for supported version skew, upgrade order, and configuration changes.
Deployment
Install charts/dsx-identity once per identity
shard with Helm. When enabled, the parent chart creates DPF DPUService resources
that reference the DSX IMDS and
DPU token-fetcher admission child charts.