Skip to main content
Search

# Kubernetes

11 related articles

Subscribe to updates
  1. GPU platform validation gains a runtime inventory: AICR now ships k8s-aibom by default, showing what actually runs on each node

    NVIDIA's open-source AICR now includes Google's k8s-aibom as a qualified component in its recipes, so a GPU-accelerated Kubernetes platform can deploy a known-good configuration while recording which AI workloads actually run in the cluster. Previously a recipe fixed only the platform configuration, and workloads updated independently by application teams, plus mutable tags like :latest, could leave two nodes running different code under the same tag. Two GKE recipes select the component by default, and others can opt in at generation time.

  2. NVIDIA Blog

    NVIDIA hands its agent-security runtime OpenShell to CNCF, adding a governance layer for agents on Kubernetes

    At KubeCon + CloudNativeCon, NVIDIA said it is donating OpenShell, an open source runtime for securing and governing autonomous agents, to the Cloud Native Computing Foundation (CNCF) as a Sandbox project, while also contributing to Google-led Agent Substrate and releasing three new components of the DSX AI Factory Platform. OpenShell applies deterministic controls to agent activity so teams can enforce policies as agents use tools, access inference services and execute workloads, and its extensible architecture connects their own compute, inference providers, credential storage and monitoring tools. NVIDIA says hundreds of organizations have put OpenShell to use and the project has received tens of thousands of contributions in less than a year since launch.

  3. Agent Substrate enters the CNCF Sandbox: idle agent sessions are checkpointed out, with the project claiming 10x container density

    NVIDIA has donated Agent Substrate, an open-source runtime for running large numbers of sandboxed AI agents on Kubernetes, to the CNCF Sandbox. Agents spend most of their time waiting on a prompt, a tool result or a model response; keeping one Pod per session holds memory for idle sessions, while creating Pods on demand pays a multi-second cold start at every step and loses state. Agent Substrate multiplexes many sessions over a small pool of warm worker Pods, checkpointing idle sessions including memory and filesystem and restoring them onto whichever worker is free, and the project reports 10x higher density than standard containers.

  4. NVIDIA open-sources Snapshot: initialized GPU inference workloads become reusable artifacts, cutting replica restore to under 45 seconds

    NVIDIA has open-sourced NVIDIA Snapshot, a checkpoint-and-restore component for GPU inference workloads on Kubernetes that captures a fully initialized workload, including CPU and GPU memory, as a portable artifact and restores it on nodes with the same GPU model and driver, skipping weight loading, compilation and graph capture. Across vLLM, SGLang and TensorRT LLM, from a 600-million-parameter model to mixture-of-experts models with 1 TB checkpoints on eight GPUs, every tested configuration restored a replica in under 45 seconds, 8x to 36x faster than a cold start.

  5. NVIDIA hands DGX SuperPOD operations to AI agents: cross-layer root-cause hunting, read-only access first

    NVIDIA built the AI Factory Operations Agent for its own DGX SuperPOD operations so site reliability engineers no longer have to check compute, network, hardware and scheduling dashboards one by one. The agent is a set of domain-specific sub-agents that communicate over MCP, detect failures in production, correlate root causes across layers and surface recommendations through a chat interface. The framework runs as a Kubernetes control-plane application, its tool calls are constrained by read-only credentials and RBAC, and the orchestration framework is released as experimental open source software.

  6. A new framework no longer waits on an adapter: NVIDIA Workload Map describes Kubernetes jobs in one reusable YAML

    NVIDIA has moved the structural description of distributed Kubernetes jobs out of adapters compiled into tools and into a readable definition. Workload Map, a custom resource plus a Go library, gives JobSet, PyTorchJob, RayCluster and other frameworks one structural view. Previously each custom resource needed its own adapter to interpret roles, turn status into phases and edit pod templates without breaking the job, so support for a new type often waited for a release. Definitions state template paths, replica counts and status mappings in YAML, shared by schedulers and platforms; a worked JobSet resolves into one leader and two workers totaling 12 GPUs.

  7. GPUs stop being handed out whole: CUDA 13.4 enforces a memory boundary, and Kubernetes carves cards into fractions

    NVIDIA CUDA 13.4 adds an application-transparent time-sharing mode that confines each workload to a fraction of GPU memory, so an allocation above the requested size fails as it would on a smaller GPU. KAI Scheduler offers an NvFractions sharing mode from v0.18.0 that picks GPU slices and writes memory and compute mode into Pod annotations, and the new open-source gpu-fractioning operator enforces those limits on each node and measures per-fraction use.

  8. NVIDIA Puts Its Self-Healing Recovery Engine on Kubernetes: Faulty Nodes Get Isolated While Training Jobs Restart Without Waiting for Root Cause

    NVIDIA Mission Control 2.5 extends an autonomous recovery engine that previously served only Slurm high-performance computing workloads to Kubernetes workloads managed by NVIDIA Run:ai. Such AI factories had relied on manual intervention, static checkpointing and reactive monitoring, which does not scale to dozens of concurrent multi-node training jobs. The release splits recovery into three coordinated layers: workload placement, job recovery that uses failure history and job topology to choose restart, retry or requeue, and hardware recovery that isolates suspect nodes and runs diagnostics, so recovery need not wait for root-cause analysis.

  9. arXiv

    An SRE agent stops starting from scratch: it writes detectors and playbooks, resolving recurring faults 2.1x faster

    SDO, an operator agent for Kubernetes applications, distills each resolved incident into reusable operational memory: parameterized playbooks that record diagnosis and repair steps, non-LLM detectors that decide from cluster state which playbook applies, and an architecture summary that binds playbook roles to the current application. Across 11 open-source microservice applications, SDO cuts resolution time on recurring faults by 52%, with median resolution falling from 584 s to 282 s and tokens from 5.4M to 2.2M; when deploying applications from source, operational memory reduces deployment time and token use by 47.5%.

  10. NVIDIA open-sources NVCRE: running real distributed workloads on Kubernetes turns pre-512-GPU-training cluster readiness into a provable property

    NVIDIA released NVCRE (Cluster Readiness Engine), an open-source Kubernetes controller that runs real distributed workloads (NCCL communication, DCGM level-4 diagnostics, NeMo Nemotron 5 pretraining), measures results across topology-aware node groups, and reports exactly which nodes failed and why, verifying GPU cluster readiness before production workloads land instead of hand-writing NCCL manifests and bisecting racks manually.