Token-fetcher user guide
The injected dsx-token-fetcher sidecar exchanges the workload’s local SPIRE
JWT-SVID for a DSX JWT and refreshes the token file before expiry. NVIDIA
Workload Identity must have Pod token fetching enabled.
Kubernetes Pods
Add the service label and token-fetcher annotations to the Pod template:
Use the relying party’s audience. For a Pod, put the labels and annotations
directly under metadata.
Application containers receive the token through a read-only mount:
Apply non-dpf-pod.yaml and wait for the example token
reader to become ready:
DPUService Pods
Configure the external DPF identity templates
and opt the DPUService into SPIFFE registration. The example packages a
token-fetcher-enabled DaemonSet in the
dsx-token-fetcher-example chart:
Set the audience and pin the chart version for persistent environments, then
apply dpu-service.yaml:
Consume the token file
Cache the token and watch /run/secrets/nvidia.com/dsx, not the token file
inode. Refresh replaces the file atomically. Reread on directory changes and on
a polling interval in case a change event is lost:
The fetcher preserves an unexpired token after a failed refresh and removes it after expiry. Treat an empty cache as an authentication failure. See Consume a DSX JWT to use the token.