Posted on November 3, 2026 by Zhen Zhang, OpenKruise Maintainer OpenKruise Agents is a sub-project of OpenKruise, the CNCF open-source application automation and workload orchestration project. It provides full lifecycle management for Agent Sandboxes running at scale on Kubernetes, together with a complete runtime environment covering networking, storage, and identity. OpenKruise Agents exposes both Kubernetes and E2B interfaces , so infrastructure teams, platform teams, and AI algorithm engineers can all operate sandboxes conveniently.
0 release answered one question: once a Sandbox is handed to an Agent, how do you upgrade it, resize it, and account for it. Its roadmap closed with two promises — network governance through TrafficPolicy / SecurityProfile , and a security identity integration that keeps platform credentials out of Agent code. 0 delivers both, and adds the operational machinery around them: 283 merged pull requests and 27 new contributors since v0. This post covers four capabilities in depth: Together these deliver three kinds of customer value: security hardening , operational capability , and cost optimization .
The post is organized in three parts: the architecture changes that made them possible, a deep dive into the four capabilities, and the value summary and roadmap. 0 was a workload layer, v0. 0 is a workload layer with its own data plane . Traffic inspection, policy distribution, and identity all became first-class components rather than external add-ons. The overall architecture: From four components to six. 0 adds traffic-control-plane and traffic-proxy : Two consequences are worth internalizing.
First, egress is no longer the Pod's own business — it is captured in-pod, routed through an egress gateway, and decided by a policy engine that sees the full request, not just the socket. Second, the ingress gateway can wake a sandbox , which is what makes wake-on-traffic possible without an external poller. what makes wake-on-traffic possible without an external poller. The CRD count doubled from 6 to 12 , adding PoolAutoscaler , TrafficPolicy , GlobalTrafficPolicy , SecurityProfile , and GlobalSecurityProfile — a multi-tier control system spanning cluster, tenant, and sandbox scopes.
