THE WORLD IS NOT STANDING STILL.RSS
BIG CHANGE.
BIG CHANGE, one tap away
BIG CHANGE, one tap away

Make room for the big picture.

Add BIG CHANGE to your home screen or desktop. It opens in its own window, with the latest stories when you’re online.

iPhone & iPad
Open bigchange.ai in Safari. Tap Share, then Add to Home Screen. Turn on Open as Web App if shown, then tap Add.
Android
Open bigchange.ai in Chrome. In the browser menu, choose Install app or Add to Home screen.
Desktop
In Chrome or Edge, use the install icon in the address bar or the browser’s app menu. In Safari on Mac, choose File → Add to Dock.

Markdown edition

# NVIDIA previews Kubernetes recipes for Vera Rubin

> NVIDIA describes an early-tested cluster configuration.

By BIGCHANGE.AI Editorial

Published: 2026-11-03T20:00:38.334Z
Updated: 2026-11-03T20:00:38.334Z
Canonical: https://bigchange.ai/blog/nvidia-vera-rubin-kubernetes-recipes

![Conceptual illustration of a generic server cabinet in a data-centre aisle, with cables routed along overhead trays.](https://bigchange.ai/api/media/file/cuda-shared-compute-hero-v1.png)
AI-generated conceptual illustration by BIG CHANGE.

On November 2, NVIDIA reported preview Kubernetes recipes tested on early Vera Rubin NVL72 reference clusters.

## The big change

- Versioned recipes help teams reproduce a known cluster configuration.
- Passing validation does not mean the recipe is production-qualified.
- Operators must check the recorded revision before applying validation to changed recipes.

## Why a recipe matters

NVIDIA AI Cluster Runtime (AICR) packages compatible driver, operator and operating-system choices as versioned recipes. Its earlier v1.0 announcement described generating deployment bundles and checking a running cluster against the chosen configuration. This gives teams a reproducible starting point, while their own environment still needs verification.

BIG CHANGE previously covered [cluster training recovery](https://bigchange.ai/blog/nvidia-mission-control-2-5-kubernetes-training-recovery).

The tested stack includes an R615.23 driver, Ubuntu 26.04 and DRA driver v0.5.0. Training and inference configurations passed NVIDIA's deployment and conformance checks. The recipes lack supported-release lifecycle qualification. An unmapped Rubin architecture caused DRA plugin crashes during early validation; NVIDIA says driver v0.5.0 includes the fix.

## What the test covers

Kubernetes dynamic resource allocation uses claims to request devices and schedules a workload where the requested resources are available. A driver and node components then configure device access. That separation matters when a distributed workload needs a consistent set of resources rather than simply counting GPUs.

NVIDIA reports a cross-node NVLink all-reduce test using ComputeDomains. This is not a training benchmark or customer deployment. Validation excluded multi-instance GPU profiles and ConnectX-9 RDMA performance.

NVIDIA says its then-current recipe would mismatch the signed historical digest. Operators must verify software, network and workload; production support or universal performance remains unproven.

## Sources

- [NVIDIA Vera Rubin validation](https://developer.nvidia.com/blog/making-kubernetes-ai-ready-for-nvidia-vera-rubin-on-day-one/) — Vendor account of preview recipes and tests.
- [NVIDIA AICR v1.0](https://developer.nvidia.com/blog/aicr-v1-0-open-stable-and-verifiable-gpu-cluster-configuration/) — Earlier runtime and verification design.
- [Kubernetes 1.34 DRA](https://v1-34.docs.kubernetes.io/docs/concepts/scheduling-eviction/dynamic-resource-allocation/) — Device allocation model.