NVIDIA/aicr

Tooling for optimized, validated, and reproducible GPU-accelerated AI runtime in Kubernetes

What it solves

Running GPU-accelerated Kubernetes clusters is often unreliable because small mismatches between kernel versions, drivers, container runtimes, and Kubernetes releases can cause difficult-to-diagnose failures. AI Cluster Runtime (AICR) eliminates this guesswork by providing version-locked, validated configurations called "recipes" that ensure the right combination of software and hardware is used for a specific workload.

How it works

AICR uses a recipe engine that matches a user's target environment (cloud provider, GPU type, OS, and workload intent) against a library of validated overlays and mixins. It then uses a bundler to convert these recipes into deployment-ready artifacts for popular GitOps tools like Helm, Argo CD, Flux, and Helmfile. To ensure the cluster is running as intended, a Snapshot Agent captures the live state of the cluster, which the AICR validator then compares against the original recipe to check for configuration drift or performance issues.

Who it’s for

Platform engineers and DevOps teams who manage GPU-accelerated Kubernetes clusters for AI training and inference workloads across various cloud providers (AWS, GCP, Azure) or on-premises environments.

Highlights

  • Multi-Deployer Support: Generates compatible bundles for Argo CD, Flux, Helm, and Helmfile.
  • Comprehensive Validation: Includes multi-phase validation for deployment, performance (training/inference), and conformance.
  • Supply Chain Security: Implements SLSA Build Level 3 provenance, signed SBOMs, and image attestations using Cosign/Sigstore.
  • Drift Detection: Ability to compare cluster snapshots to identify configuration changes over time.
  • Broad Hardware Support: Validated for a wide range of NVIDIA GPUs, including H100, A100, B200, and L40S.

Related

  • Project
  • Project
  • Project
  • Project
  • Project