NVIDIA AICR Adds Qualified AIBOM Support for Kubernetes AI Workloads
NVIDIA says its open-source AI Cluster Runtime (AICR) now includes a qualified AI bill of materials component that integrates Google's k8s-aibom to inventory recognized AI workloads on Kubernetes. The integration supports version-locked deployment bundles, provenance and security-default checks, and per-namespace opt-in inventory, while NVIDIA reports low controller overhead in a GKE test using k8s-aibom v1.6.1. Runtime observations are not signed by default, and linking them with verified provenance and deployment intent remains unfinished work.
The integration gives platform teams a way to record which supported AI workloads and artifacts are actually running on Kubernetes, adding runtime inventory to AICR's reproducible GPU deployment bundles.
As teams deploy and scale AI workloads using NVIDIA Dynamo, Kubeflow, or Slurm, tracking what actually runs requires visibility beyond the platform configuration captured in a recipe. Application teams define and update these workloads independently of the platform recipe, so a reproducible deployment bundle alone cannot establish which workload artifacts are running on each node. Mutable image tags like :latest add another layer of complexity. Two nodes can end up running different code under identical tags, and a node that pulls next week may retrieve an image that was not covered by an earlier security review.
NVIDIA AI Cluster Runtime (AICR), an open source modular component of the NVIDIA DSX AI Factory Platform, now includes a qualified AI bill of materials (AIBOM) component to close that gap. An open source project created by Google, k8s-aibom tracks AI workloads running on Kubernetes. Two stock recipes select k8s-aibom by default: h100-gke-cos-inference and h100-gke-cos-inference-dynamo. Other GKE recipes can opt in during generation with --runtime-inventory enabled. Recipes selecting it can opt out with --runtime-inventory disabled.
AICR turns known-good GPU platform configurations into version-locked recipes and reproducible deployment bundles. Each recipe records the desired configuration for one hardware, cloud, OS, and intent combination: its components, version pins, values, constraints, deployment ordering, and validation expectations. AICR generates reproducible deployment artifacts from fixed recipe, catalog, and bundle inputs. Bundles include checksums; signing is optional through aicr bundle --attest.
#NVIDIA#NVIDIA AI Cluster Runtime (AICR)#Google#k8s-aibom#NVIDIA DSX AI Factory Platform#Google Kubernetes Engine (GKE)#NVIDIA Dynamo#NIMService#LeaderWorkerSet#DisaggregatedSet#CycloneDX