Skip to content

v0.22.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 21 Sep 21:02
· 557 commits to main since this release
Immutable release. Only release title and notes can be modified.
v0.22.0
This tag was signed with the committer’s verified signature.
mchmarny Mark Chmarny
SSH Key Fingerprint: GvwYDxrKzpkXGzFjtmQ26NvM9ij3PeD/qnNvBmT67zE
Verified
Learn about vigilant mode.
7e3078d
This commit was signed with the committer’s verified signature.
mchmarny Mark Chmarny
SSH Key Fingerprint: GvwYDxrKzpkXGzFjtmQ26NvM9ij3PeD/qnNvBmT67zE
Verified
Learn about vigilant mode.

As our last v0 release before v1 (scheduled on October 5th), this release focuses on component upgrade safety, validation hardening, and bundler and deployer reliability, landing alongside new platform and accelerator coverage and the last phase of ADR-022 described apiVersion migration that v1.0.0 will complete.

Highlights

Component Upgrade Safety - v1 commits AICR to safe component upgrades, and this release adds additional capabilities to that mechanism. ADR-021 defined a transition record, a per-component, per-version-boundary statement of safe, manual, or blocked, with the steps and the evidence that backs it, and a fail-closed loader that reports unknown rather than guessing. The new aicr upgrade-check command reads those records and reports the verdict for the boundary you are about to cross. Records also live beside the component they describe, so the obligation renews on each pin bump rather than decaying.

Validation Hardening - Every check that v1 will stand behind has to fail for the right reason. The DRA support check now gains an MNNVL IMEX channel subtest. The NCCL benchmark is derived from the shipped TCPXO runtime rather than a separately pinned image, with AICR_NCCL_RUNTIME_IMAGE available where a site needs its own. The GB200 NET preflight is now driver-version-aware, unsupported Hyperdisk types are rejected on a4x nodes, AKS cluster autoscaling is validated, NodeWright is read by discovery, and Job deadlines get headroom over the check budget so a slow check fails as a check rather than a timeout.

Bundler and Deployer Reliability — The bundle layout is a frozen v1 surface, so what it emits has to be right on every deployer, not just the common one. bundle-info.yaml now records the deployer and layout that produced the bundle. recipe.yaml is written for every deployer, not only Helm; ownsCRDs is honored on the helm and helmfile deployers; helm connection flags are translated for the CRD step, with the flag value redacted when the step rejects it; and dry-run no longer previews a stale cached chart archive.

Recipes and Coverage

  • k0s joins the supported services, with a validated H200 training leaf, a setup guide, and Preview coordinate coverage
  • GKE gains a GB200 (a4X) recipe with NVLS NCCL validation, and a torch-distributed-tcpxo runtime with the network mapping TCPXO requires
  • Five new training-kubeflow leaves, each with its evidence link kept intact
  • GB300 gets node tuning enabled and bumped NodeWright packages, plus its own NCCL thresholds
  • Kueue moves to 0.19.3 and kai-scheduler to v0.16.9

Other Improvements

  • Five opt-in NVSentinel mixins widen what a cluster reports about itself: audit logging and tracing, a Kubernetes Object Monitor, a preflight mixin, Node Problem Detector conditions consumed as NVSentinel signal, and NIC and fabric fault detection on Mellanox platforms.
  • SLSA provenance is attested per platform manifest; recipe digests are content-only via PredicateTypeV3; evidence fails closed on a mutable validator image tag; and overlay recipe digests are canonicalized so the same recipe hashes the same way
  • New signed evidence for GB300 EKS training and inference, VR200 training-kubeflow, and the H100 AKS training-kubeflow and inference-dynamo coordinates
  • A recipe can pin deployment identity so registry defaults can move underneath it; a profile value can tighten a composed constraint; and a direct -r overlay whose mixins were not applied is rejected rather than silently under-resolved

Thanks to @ArangoGutierrez, @atif1996, @ayuskauskas, @chris320211, @coffeepac, @lockwobr, @mikecook, @mohityadav8, @njhensley, @ramessesii2, @rorajani, @srao-nv, @sylvesterkaczmarek, @varmesh, @vineeth-bandi, @yuanchen8911, and @mchmarny.

Changelog

New Features

Bug Fixes

Other Tasks

Contributors

mchmarny, coffeepac, and 16 other contributors
Assets 22
Loading