Skip to navigation

DSX IMDS

View as Markdown

metadata-service implements DSX IMDS. It serves DSX JWTs through the IMDS v1 API, selects a local SPIRE JWT-SVID by hint, exchanges it, and returns the DSX JWT. KubeVirt uses NVIDIA Workload Identity Keys Proxy CSI. Paired-DPU placement uses a direct URL to its reachable shard-local NVIDIA Workload Identity Keys. Each process configures exactly one --identity-keys-url, whose scheme selects the transport. For a Unix proxy to an HTTPS virtual host, set --identity-keys-host to that route’s DNS name so the exchange request carries the matching HTTP Host header.

GET identity with Metadata: true and aud Request local SPIRE JWT-SVID by hint Local SPIRE JWT-SVID RFC 8693 request over Unix socket Forward request over verified TLS Exchanged DSX JWT JSON object or plain DSX JWT KubeVirt VM external client virt-launcher DSX IMDS sidecar dsx_imds-attested host SPIRE agent process NVIDIA Workload Identity Keys Proxy CSI socket Shard-local NVIDIA Workload Identity Keys Pod

The same binary serves the dsx-imds host identity behind the paired DPU intercept and NICo IMDS passthrough, and serves the dsx-imds-vm identity as a KubeVirt sidecar. The identity chart injects that sidecar through charts/dsx-identity/templates/vm-support.yaml. DPF deploys the same binary on DPU nodes through charts/dsx-imds.

For KubeVirt, the guest initiates the metadata request. The operator-owned virt-launcher Pod and tenant-facing VM identities use the same operator worker host’s Workload API. The Pod keeps the configured operator tenant while the VM identity uses the tenant supplied by its LaunchLayer source. The exact dsx-imds-vm hint selects the VM identity. It does not select a separate SPIRE agent path. The Kubernetes WorkloadAttestor serves the operator virt-launcher Pod identity, SPIFFE CSI exposes the same host agent socket to the sidecar, and NVIDIA Workload Identity Keys Proxy CSI carries the exchange request to the shard-local NVIDIA Workload Identity Keys.

VM identity trust path

The VM SPIRE JWT-SVID remains inside the virt-launcher Pod. DSX IMDS exchanges it through the proxy and serves only the resulting DSX JWT to the VM.

Workload API socket mounted socket fetch from mounted socket exchange through proxy IMDS request served through IMDS Bare-metal host SPIRE agent process SPIFFE CSI node plugin Pod virt-launcher PodDSX IMDS (metadata-service) sidecar NVIDIA Workload IdentityKeys Proxy CSInode plugin Pod Shard-localNVIDIA Workload IdentityKeys VM SPIRE JWT-SVID VM DSX JWT KubeVirt VM

VM IMDS request path

The guest supplies the metadata header. The exact dsx-imds-vm hint selects the VM SPIRE JWT-SVID before the proxy carries the exchange request.

Workload API socket mounted socket IMDS requestMetadata: true fetch dsx-imds-vm hinted SVID exchange through proxy served through IMDS Bare-metal host SPIRE agent process Host-provisioned SPIFFE CSInode plugin Pod virt-launcher PodDSX IMDS (metadata-service) sidecar NVIDIA Workload IdentityKeys Proxy CSInode plugin Pod Shard-localNVIDIA Workload IdentityKeys Deployment VM SPIRE JWT-SVID VM DSX JWT KubeVirt VM guest

HTTP API

The supported identity endpoints are:

GET /latest/meta-data/identity?aud=<audience>
GET /2009-04-04/meta-data/identity?aud=<audience>
GET /latest/meta-data/identity?aud=<audience>
Metadata: true
Accept: application/json

Requests require Metadata: true, reject proxy forwarding headers, and may repeat aud. Accept supports application/json and text/plain. An absent header defaults to JSON. Plain text returns only the DSX JWT. JSON returns token, expires_in, and spiffe_id. Successful identity responses use Cache-Control: no-store. Response connections use IPv4 TTL 1 or IPv6 hop limit 1. Dependency failures return sanitized HTTP errors. GET /health reports process health.

KubeVirt guests reach DSX IMDS at 169.254.169.254 over IPv4 and fd00:76b9::254 over IPv6. The network setup sidecar configures the endpoints for the address families in the primary OVN allocation. Both bridge and l2bridge bindings require the OVN-allocated guest address and MAC. See the network setup README for guest routing.

curl --noproxy '*' -g -H 'Metadata: true' \
'http://[fd00:76b9::254]/latest/meta-data/identity?aud=spiffe://ds9.dsx.nvid.id/openbao'
{"token":"<DSX JWT>","expires_in":300,"spiffe_id":"spiffe://tenant-2.ds9.dsx.nvid.id/vm/vm-1234"}

The API is intentionally tokenless. The paired DPU intercept and NICo enforce physical source binding, network isolation, and response hop limits. Metadata: true and proxy-header rejection are additional request checks, not a replacement for that network boundary.

Flags

FlagDefaultPurpose
--listen:80HTTP listen address
--identity-keys-urlrequiredRFC 8693 HTTP endpoint, or unix:///path/to/socket for NVIDIA Workload Identity Keys Proxy CSI
--spire-socket/var/run/secrets/spire.io/spire-agent.sockSPIRE Workload API socket path
--svid-hintdsx-imdsExact identity hint, either dsx-imds or dsx-imds-vm
--log-levelinfoJSON log level: debug, info, warn, or error