Skip to navigation

DSX Token Fetcher

View as Markdown

dsx-token-fetcher obtains a local SPIRE JWT-SVID from the Workload API, submits it to the local NVIDIA Workload Identity Keys, and writes the exchanged DSX JWT-SVID to a shared file. In long-running mode it refreshes the token before expiry and reports readiness at /healthz.

request local SPIRE JWT-SVID RFC 8693 request exchanged DSX JWT-SVID atomic file replacement read DSX JWT-SVID dsx-token-fetcherprocess or Pod sidecar Local SPIRE agent process Shard-localNVIDIA Workload IdentityKeys DSX JWT-SVID token file Pod consumer

The identity chart injects the sidecar and shared volume through charts/dsx-identity/templates/pod-token-fetcher.yaml. The spiffe.nvidia.com/inject-dsx-token-fetcher: "true" annotation selects injection. Each selected Pod supplies its token audience through the spiffe.nvidia.com/token-audience annotation. The spiffe.nvidia.com/service label independently selects SPIRE registration. The fetcher writes the DSX JWT-SVID to the shared Pod volume.

Flags

FlagDefaultPurpose
--socketunix:///var/run/secrets/spire.io/spire-agent.sockSPIRE Workload API socket URL
--audiencespiffe://example.orgAudience requested in the local SPIRE JWT-SVID
--svid-hintemptyOptional exact SPIRE JWT-SVID hint override. Without it, use the Workload API default
--identity-keys-urlrequiredRFC 8693 endpoint of the reachable NVIDIA Workload Identity Keys
--output/run/secrets/nvidia.com/dsx/tokenDSX JWT-SVID output file
--health-port8080Port for /healthz
--log-levelinfoLog level: debug, info, warn, or error

The runtime owns access to the output directory. The fetcher atomically replaces the consumer-readable token file. A failed refresh keeps an unexpired token available. An expired token is removed and readiness returns HTTP 503. Long-running fetchers refresh after 80 percent of the remaining lifetime. The fetcher retries failed refreshes once per second.