On 11 November 2026, NVIDIA described an integration that adds an AI bill of materials (AIBOM) for supported Kubernetes workloads to NVIDIA AI Cluster Runtime (AICR), part of the DSX AI Factory Platform. The company says the integration combines version-locked GPU platform recipes with workload inventory from the open-source k8s-aibom project.[1]

AICR recipes record desired platform configuration, while k8s-aibom watches workload and pod APIs and produces CycloneDX 1.6 records for recognized AI workloads. Two H100 Google Kubernetes Engine recipes select the inventory component by default; other GKE recipes can opt in. NVIDIA's example uses AICR v1.2.0 with a catalog that pins k8s-aibom 1.6.2.[1]

The inventory covers supported workload kinds with a recognized AI signal in namespaces opted in for reporting. Each recorded attribute has a confidence tier and an evidence locator. An AIBOM can exist before a pod runs: it records the workload specification and, when a pod exists, available resolution evidence. It does not establish successful execution. The namespace label controls which records are emitted, while the controller still caches workload and pod specifications cluster-wide.[1]

NVIDIA says its qualification process binds specific upstream artifacts and a digest-pinned controller image, checks provenance and exercises deployment operations on tested paths. Runtime observations themselves are unsigned, model-claim signature verification is disabled by default, and connecting platform provenance to runtime inventory remains future work. A matching storage version alone also does not establish that the full custom resource definition schema is current.[1]

Sources

  1. Validating GPU Platforms with Runtime AI Inventory via the NVIDIA DSX AI Factorydeveloper.nvidia.com · 11 Nov 2026

Check or correct this page

Verification record

The digest below shows whether the text you are reading matches the published source. It does not show that the reporting is correct. The build computes it from this page's Markdown source and lists it in the site manifest.

a67dadc3c59e16968d90014bc13ea1dd607acfb2240f43f1fe5b6cf2e6ce0fbc