Skip to navigation

Identity contract

View as Markdown

DSX JWT subjects use complete key/value pairs with unique keys:

spiffe://<tenant>.<region>.<service>.<partition>/<key>/<value>[/<key>/<value>...]
spiffe://<operator-tenant>.<region>.<service>.<partition>/bm/<node-name>/pod/<pod-uuid>
[/role/<role>]

DPU service identities use:

spiffe://<operator-tenant>.<region>.<service>.<partition>/dpu/<serial>/dpuservice/<service-id>/namespace/<namespace>

Exchange preserves path keys and values exactly. For example:

local: spiffe://<local-domain>/tenant/<tenant>/service/dsx/cluster/cluster-1/namespace/team-a/workload/api
exchanged: spiffe://<tenant>.<region>.dsx.<partition>/cluster/cluster-1/namespace/team-a/workload/api

Path keys and values retain their case and order. Each segment starts with an ASCII letter or digit, followed by ASCII letters, digits, ., _, or -.

Cluster-local SPIRE identities encode the same fields under the shard trust domain. Exchange takes the region and partition from explicit configuration, the tenant and service from the local subject, and preserves the resource path.

spiffe://<local-trust-domain>/tenant/<tenant>/service/<service>/<key>/<value>[/<key>/<value>...]
ResourceTenant sourceSubject resource path
DPUOperator tenant in DPF identity templates/dpu/<normalized-serial> resource prefix
DPU-paired operator bare-metal hostglobal.operatorTenant/bm/<dpu-machine-id>
Operator bare-metal Kubernetes workerglobal.operatorTenant/bm/<node-name>
Kubernetes Podglobal.operatorTenant/bm/<node-name>/pod/<pod-uid>
Bare-metal host with a Launch Layer sourcelaunchlayer.nvidia.com/org-id annotation/bm/<bm-id>
VM with a Launch Layer sourcelaunchlayer.nvidia.com/org-id annotation/vm/<vm-id>

Every Kubernetes worker is an operator-owned bare-metal host. There is no configured worker list and no LaunchLayer source for these hosts. The Pod registration template derives the host ID directly from the Kubernetes node name. The DPU source supplies the BM resource ID through its carbide.nvidia.com/dpu-machine-id label.

Every DSX Kubernetes Pod supplies its service label. SPIRE uses its value for the service path segment. The fixed parent template identifies the worker’s operator-tenant dsx_imds agent.

metadata:
labels:
spiffe.nvidia.com/service: dsx
spiffe.nvidia.com/role: database # optional
spire:
spire-server:
controllerManager:
extraEnv:
- name: OPERATOR_TENANT
value: operator-1
parentIDTemplate: 'spiffe://{{ .TrustDomain }}/spire/agent/dsx_imds/tenant/$OPERATOR_TENANT/bm/{{ .NodeMeta.Name }}'

The chart requires the controller-manager value to equal global.operatorTenant. Because it is part of the SPIRE Pod template, changing both values causes the StatefulSet to roll out without a restart hook.

The paired host identity is a controller-derived static entry parented to the external dpu_hw agent identified by the normalized DPU serial. DPUs are Kubernetes nodes in their Kamaji clusters. The DPU agent’s Kubernetes WorkloadAttestor identifies the IMDS Pod, and SPIFFE CSI exposes the agent’s Workload API socket to that Pod.

The NVIDIA Workload Identity Controller derives SPIRE registration entries from DPU and Launch Layer sources.

apiVersion: launchlayer.nvidia.com/v1alpha1
kind: VirtualInstance
metadata:
annotations:
launchlayer.nvidia.com/org-id: tenant-2
spec:
instance_id: vm-1234
node_name: host-1234
status:
pod_uid: <virt-launcher-pod-uid>

BareMetalInstance uses the same tenant annotation, spec.instance_id, and status.primary_dpu.machine_id plus status.primary_dpu.serial_number. The configured operator tenant determines a VM entry’s worker parent. The Identity Controller owns these entries’ SPIFFE IDs, selectors, hints, and class names.

DPU identities

DPF registers the DPU Agent process and opted-in DPUService workloads beneath the DPU’s spiffe://<local-trust-domain>/spire/agent/dpu_hw/<normalized-serial> agent ID. These workload subjects use the /dpu/<normalized-serial> resource prefix. The paired host’s /bm/<dpu-machine-id> identity is a separate entry owned by the NVIDIA Workload Identity Controller. A complete tenant BareMetalInstance replaces that operator host entry with /bm/<spec.instance_id> under the assigned tenant.

See the identity chart configuration for the DPF templates used to produce these subjects.

NVIDIA Workload Identity Keys and Event Bus

NVIDIA Workload Identity Keys validates local SPIRE JWT-SVIDs and issues DSX JWTs. By default it publishes public signing keys to the Event Bus and serves aggregate JWKS. With NATS disabled it serves only local public signing keys. The external Gateway terminates TLS and applies source-aware request quotas. Clients configure the Gateway HTTPS endpoint.

DSX IMDS host and VM flows

DSX IMDS serves the tokenless host and VM identity API. The dsx_imds NodeAttestor agent and dsx_imds NodeAttestor server bootstrap the host SPIRE agent. The NVIDIA Workload Identity Keys Proxy CSI Driver carries VM exchange requests, and DSX IMDS Network Setup routes the VM’s metadata traffic to 169.254.169.254 over IPv4 and fd00:76b9::254 over IPv6. It configures the address families present in the primary OVN allocation, including IPv4-only, IPv6-only, and dual-stack guests.