DSX Token Fetcher
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 to a shared file. In long-running mode it refreshes the
token before expiry and reports readiness at /healthz.
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
to the shared Pod volume.
Flags
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.