{"slug": "google-donates-agent-substrate-and-gvisor-to-the-cncf-to-secure-ai-agents-at", "title": "Google Donates Agent Substrate and gVisor to the CNCF to Secure AI Agents at Scale", "summary": "Google donated its Agent Substrate and gVisor projects to the Cloud Native Computing Foundation (CNCF), along with open-source reinforcement learning orchestration project OpenRL, placing core AI agent infrastructure under vendor-neutral governance. Google says Agent Substrate separates agent state (actors) from pre-warmed compute (workers) so agents can resume in under 500 milliseconds without creating a new Kubernetes Pod per execution, while gVisor adds a user-space application kernel as an isolation boundary for untrusted AI-generated code. Google estimates agents can spend 90-95% of their time idle while still holding state such as memory, files, repositories and active sessions.", "body_md": "Google has [announced](https://opensource.googleblog.com/2026/11/sandboxing-untrusted-ai-agents-at-scale.html) it is donating [Agent Substrate](https://github.com/agent-substrate/substrate) and [gVisor](https://gvisor.dev/) to the [Cloud Native Computing Foundation (CNCF)](https://www.cncf.io/), placing two important components of its AI agent infrastructure under vendor-neutral open-source governance. The move is intended to address two emerging challenges in running autonomous agents at scale: securely executing untrusted, AI-generated code and managing the substantial compute overhead created by agents that frequently pause and resume.\n\nThe announcement also includes [OpenRL](https://openrl.dev/), Google's open-source reinforcement learning orchestration project. Together, the projects target different layers of agent infrastructure, from isolated code execution to managing agent lifecycles and coordinating large-scale training workloads. The goal is to establish an open foundation for agentic applications, much as [Kubernetes](https://kubernetes.io/) helped standardise container orchestration.\n\nGoogle argues that conventional Kubernetes workloads and AI agents have fundamentally different execution patterns.\n\nA traditional application typically starts, serves requests, and continues running. An AI agent, however, may execute a tool or code for a few seconds before waiting for model inference, an external API, or human approval. Google estimates that agents can spend 90-95% of their time idle while still holding important state, including memory, files, repositories, and active sessions.\n\nKeeping every agent in a dedicated Pod wastes resources, while scaling to zero introduces delays when environments must be reconstructed. At the other extreme, large-scale agent evaluations can overwhelm Kubernetes control planes when thousands of short-lived execution environments are repeatedly created and destroyed.\n\nGoogle developed Agent Substrate to address these limitations by separating agent state (actors) from the compute resources (workers) used to execute it.\n\nActors represent individual agent sessions and retain their state, including filesystem contents, memory, and execution context. Workers provide reusable, pre-warmed execution environments drawn from shared Kubernetes pools.\n\nWhen an agent needs to resume, Substrate assigns it to an available Worker and restores its previous state. When the agent becomes idle, its state can be saved and the underlying compute resource released.\n\nAccording to Google, this approach lets agents resume in under 500 milliseconds without creating a new Kubernetes Pod for every execution. It also reduces pressure on the Kubernetes control plane by managing agent lifecycles independently of individual Pod objects.\n\nThe second major challenge is security. AI agents routinely execute generated shell commands, install packages, and interact with external tools. Treating this code as trusted creates significant risks, particularly when multiple agents share infrastructure.\n\nGoogle's gVisor provides an additional isolation boundary through a user-space application kernel. Instead of letting containerised applications interact directly with the host Linux kernel, gVisor intercepts system calls and handles them within its own isolated environment.\n\nThis reduces the exposure of the underlying host while retaining much of the efficiency associated with container-based execution.\n\nAgent Substrate also supports [Cloud Hypervisor microVMs](https://github.com/cloud-hypervisor/cloud-hypervisor) for workloads requiring hardware-level virtualisation. This gives platform teams flexibility to select an appropriate isolation boundary without changing the overall agent lifecycle model.\n\nThe announcement reflects a broader shift in cloud-native infrastructure. Kubernetes was designed around long-running applications and relatively stable workloads. Agentic systems introduce more dynamic execution patterns, where environments must be created, suspended, restored, and isolated at much greater frequency.\n\nOther providers are addressing similar challenges through technologies such as [Kata Containers](https://katacontainers.io/), [Firecracker](https://firecracker-microvm.github.io/), and dedicated sandboxing platforms. Google's contribution is to combine secure execution with an agent-aware orchestration model and place the resulting technologies within an open ecosystem.\n\nThe wider implication is that AI agents need more than an orchestration framework and access to tools; they need their own secure, stateful, and efficiently managed execution infrastructure. By donating these projects to the CNCF, Google is helping establish the foundations for that next layer of cloud-native computing.", "url": "https://wpnews.pro/news/google-donates-agent-substrate-and-gvisor-to-the-cncf-to-secure-ai-agents-at", "canonical_source": "https://www.infoq.com/news/2026/11/google-substrate-gvisor-cncf/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global", "published_at": "2026-11-20 12:00:00+00:00", "updated_at": "2026-11-20 12:11:40.727700+00:00", "lang": "en", "topics": ["ai-agents", "ai-safety", "ai-infrastructure", "developer-tools", "ai-policy"], "entities": ["Google", "Agent Substrate", "gVisor", "Cloud Native Computing Foundation", "OpenRL", "Kubernetes", "Cloud Hypervisor"], "also_reported_by": [], "takeaway": "Separating agent state (actors) from pre-warmed workers lets agents resume in under 500ms without a new Kubernetes Pod per execution, and gVisor's user-space kernel intercepts syscalls to isolate untrusted AI-generated code.", "recommendation": null, "alternates": {"html": "https://wpnews.pro/news/google-donates-agent-substrate-and-gvisor-to-the-cncf-to-secure-ai-agents-at", "markdown": "https://wpnews.pro/news/google-donates-agent-substrate-and-gvisor-to-the-cncf-to-secure-ai-agents-at.md", "text": "https://wpnews.pro/news/google-donates-agent-substrate-and-gvisor-to-the-cncf-to-secure-ai-agents-at.txt", "jsonld": "https://wpnews.pro/news/google-donates-agent-substrate-and-gvisor-to-the-cncf-to-secure-ai-agents-at.jsonld"}}