Google published an open-source orchestrator for running agent workloads on Kubernetes

AX is an Apache 2.0 orchestrator that treats an agent run as a declarative Kubernetes-style resource. It defines four manifest kinds under ax.io/v1alpha1. Task is a sandboxed run with CPU and memory limits. Workspace lists the Git repos, MCP servers and skill packages that get wired into every sandbox before the task starts, or takes a plain-English goal that an agent resolves on first boot. Gateway locks outbound traffic to an explicit host allowlist and injects credentials into requests. Model holds the provider, parameters and secrets. The CLI is shaped like kubectl on purpose: ax apply, ax get, ax watch, plus ax suspend and ax resume to checkpoint an idle agent and pick it up where it stopped, and ax ssh to open a shell in a running sandbox.

The project describes itself as built "to run billions of autonomous agent workloads in a cluster", running on a compute runtime it calls Agent Substrate and crediting agentic runtime research from Google DeepMind. Those are the project's own claims. Nothing in the repository measures them, and the quick start does not test them. The README opens with a warning that the core concepts, protocols and specifications are still being refined and that major breaking changes are likely before a stable release. The Hacker News thread carried 22 points and 7 comments at 37 minutes old, read this evening. The early comments ran to Google's record of sunsetting products and to a one-line remark that the k8sification of AI was always inevitable.

Why it matters: The four primitives are an opinionated answer to where isolation, network policy and model configuration live, and the answer puts them outside the agent rather than inside its harness. Anyone who has hand-rolled sandboxing and egress rules around a fleet now has a first-party reference to check their own arrangement against. Take the v1alpha1 label and the breaking-changes warning at face value. This is worth reading and comparing against this quarter. It is not worth migrating onto yet.