kgateway v2.5.1 Rejects Bad Config at kubectl apply
kgateway v2.5.1 shipped on 2026-11-06 with a change that is easy to miss in a changelog and annoying to find out about the hard way: PR #14992 adds explicit …
Read more →83 posts
kgateway v2.5.1 shipped on 2026-11-06 with a change that is easy to miss in a changelog and annoying to find out about the hard way: PR #14992 adds explicit …
Read more →kagent is the runtime: it defines each agent as a Kubernetes resource, compiles it, runs the agent loop inside a Harness engine, and owns the conversation. …
Read more →Ghost actors pin your workers. A session killed mid-flight can leave its actor holding a WorkerPool slot, sometimes after that actor has disappeared from …
Read more →The autoscaler made it worse. On a model backend that generates one response at a time, adding Agent Substrate workers does not add throughput: it restores …
Read more →CPU is the wrong signal to autoscale agents. Agent Substrate workers are slot-bound, one actor per worker, and an LLM session is mostly I/O wait, so workers …
Read more →The actors list lies: every finished Agent Substrate session leaves a Suspended entry behind, so the inventory grows without bound and returns partial results …
Read more →I wanted to know whether a third-party coding agent could run as a first-class kagent agent, inside an Agent Substrate sandbox, doing platform engineering work. …
Read more →Who runs next when the agent pool is full is the question the runtime answers by accident. Agent Substrate rejects with substrate worker pool has no free …
Read more →Agent checkpoint to object storage is how Agent Substrate parks an actor’s RAM and disk so the worker slot can go to someone else. The runtime should …
Read more →Agent identity vs service account is a layering split: the SA authenticates the worker pod, and the agent needs its own principal that can be revoked per …
Read more →Zero trust architecture for AI agents means sandbox, egress, and identity, each assuming the others failed. Every action is authenticated as the agent, …
Read more →Running agents in production on Kubernetes takes a named identity for the agent, default-deny egress, a gate on tool calls, a demand signal that is not CPU, …
Read more →How many agents per Kubernetes pod is two numbers: live sessions equal workers, and registered agents equal snapshots. One live actor per worker pod at a time, …
Read more →Pod per agent is how Kubernetes wants you to run AI agents: one Deployment or Job per agent, with CPU and memory reserved for as long as the pod exists. Agents …
Read more →Agent Substrate day wrap-up is the map of the 19 topic posts under the field guide, in the order I would actually send someone the links. If you want one URL, …
Read more →Agent Substrate enterprise is a bar I would walk a platform team through, not a product name. Before I let this runtime sit under someone else’s pager I …
Read more →An Agent Substrate environment is the layer above the runtime that an agent loop actually wants: run this command, read this file, write that file, tell me …
Read more →A Kubernetes sandbox platform is what Agent Substrate still is after you ignore the word agent: a pool of sandboxes, native suspend and resume, rehydrate from …
Read more →Scheduling agent sandboxes is the job Agent Substrate does not do. It multiplexes many actors onto a small pool of warm workers, which is packing. When the …
Read more →Scheduling sandboxes for RL is a multiplexing problem: each training step fans out into sandboxes that spend most of their wall time waiting on a model. …
Read more →GPUs for agents on Kubernetes should sit outside Agent Substrate snapshots. GPU memory is not a file the runtime can checkpoint. If you give the actor a …
Read more →Suspend-safe networking is a design where an actor can be checkpointed and restored on another worker without dropping the TCP sessions it was using. I do not …
Read more →An agent platform at scale is not more pods. It is identity, scheduling, and suspend policy for fleets where most sessions are started by other agents. Replica …
Read more →kubectl is lying to you. Agent Substrate keeps the workload out of pods, so kubectl get pods shows a quiet WorkerPool while agents restore from snapshots, run …
Read more →Sandboxed networking for agents means the actor does not inherit the worker’s view of the network. Each actor needs its own isolation, default-deny …
Read more →The Agent Substrate dataplane is the path a request and a snapshot take: ateapi holds actor state, atenet routes, atelet moves checkpoint bytes, and ateom runs …
Read more →Suspend and resume agents by checkpointing the actor’s memory and filesystem to object storage, freeing the worker slot, then restoring that snapshot …
Read more →Why Agent Substrate fails, in practice, is operability and policy, not checkpoint. I was wrong that a real process would make suspend a toy. I was right that …
Read more →Proof of agent identity is evidence that this agent, not you and not the worker pod, made the call. Logs, policy, and audit have to name the agent without …
Read more →Kubernetes Network Policy for agents is the wrong grain once the agents stop being pods. A NetworkPolicy selects pods by label, so on Agent Substrate the …
Read more →kubectl is lying to you on Agent Substrate because kubectl get pods shows worker pods, not agents. Under load you will see two calm workers while actors …
Read more →Running Agent Substrate in production means real object storage for snapshots, a datastore for the control plane that survives a node loss, secrets that are …
Read more →Agent sandbox vs Agent Substrate is a three-way choice: a plain pod, a per-agent sandbox, or multiplexed snapshot-backed actors on a worker pool. Isolation is …
Read more →What is Agent Substrate? It is a Kubernetes-native runtime that treats an AI agent as a snapshot-backed actor, not as a Deployment. Idle agents are …
Read more →Agent Substrate is the Kubernetes runtime that stops treating an AI agent as a Deployment. Idle agents are snapshots in object storage: a request restores an …
Read more →Run kubectl get pods on an Agent Substrate cluster under load and you’ll see two worker pods, calm, a few MiB each. Nothing to see here. Meanwhile agents …
Read more →A paper published on arXiv on October 27 did something I hadn’t seen demonstrated end to end before: it pretrained a language model from scratch, poisoned …
Read more →The Claude Code and Codex harnesses get the attention because people already know those loops. The harness I’d actually default to is the boring one: …
Read more →I tried to break Agent Substrate’s actor checkpoint with a resource that supposedly can’t be serialized, an exclusive file lock, and it checkpointed …
Read more →The Codex post covered a runtime kagent ships for you. byo is the opposite: kagent runs your image and treats whatever’s inside as opaque. To see what …
Read more →My Claude Code harness post gets the questions. The follow-up is usually “can I do the same thing with Codex?” Yes. Here’s how, and where it …
Read more →Short version: kagent has four harnesses, and the one you pick decides what runs your agent and how much of kagent it gets to use. My Claude Code harness post …
Read more →I wrote about agent containment four days ago: default-deny egress, no ambient credentials, an audit log, one agentgateway config. All of that is a perimeter …
Read more →A CSO Online piece built around an October 2026 Hacker News thread made a direct claim: agents aren’t going rogue, frontier labs are skipping basic …
Read more →An agent runtime is the thing that starts, stops, and isolates an agent while it works. kagent puts that on Kubernetes. These posts cover the harness, the …
Read more →An AI gateway sits on the path between agents and models, tools, and other agents. It is where identity, spend, and policy get enforced once instead of in every …
Read more →OpenAI spent hundreds of billions of tokens trying to break its own agent sandboxes, and its agents won often enough to patch a Kata Containers CVE, a gVisor …
Read more →agentgateway is an open source gateway you run yourself, and it covers the jobs most teams use Portkey for: virtual keys that hide the provider key, per-key …
Read more →An MCP gateway is a proxy between AI clients and MCP servers, so agents reach many tool servers through one endpoint and every tool list and tool call passes …
Read more →Agents and apps already send prompts through a gateway. Content safety belongs on that hop: inspect the request before it reaches a model, and inspect the …
Read more →AI agents need outbound access to models, tools, registries, and APIs. An unrestricted sandbox will use every channel it can find. The durable pattern is a …
Read more →Disclosure: I work at Solo.io, which created agentgateway and sells Solo Enterprise for agentgateway. Everything below is open-source agentgateway unless it is …
Read more →On 2026-10-10, Cybernews reported that Shane Mac, CEO of XMTP Labs, gave a Grok Bot agent read-only access to his personal bank account as a finance assistant. …
Read more →Plenty of security teams already run Prisma AIRS, Palo Alto’s AI runtime security service, and they want every prompt and LLM response checked by it. I …
Read more →Coding agents grew up on laptops: one person, one machine, and one process that is the UI, the agent loop, the sandbox, the credential store and the session …
Read more →agentevals v0.10.0 shipped two days ago and removed its own WebSocket ingestion path in favor of plain OpenTelemetry. Send OTLP traces in, run an eval, and the …
Read more →An AI agent that calls tools for a user needs that user’s authority, and the usual shortcuts are a pasted personal access token or a shared service …
Read more →A production agent platform needs one gateway path where SPIFFE identity binds the caller and four controls ride the same hop: secretless provider keys, per-key …
Read more →Three replicas of an MCP server, fronted by agentgateway, with no session affinity configured anywhere. A four-call shopping cart session (create cart, add two …
Read more →I spent the last month building small, runnable labs for the ways AI agents break the infrastructure they run on: credentials, egress, audit logs, MCP tool …
Read more →Choose by the controls in the request path, not by model-catalog size. Write down what you must enforce on agent to model and agent to tool traffic: workload …
Read more →The easy way to give an agent pod access to an external API is a long-lived key in a Kubernetes Secret. The harder, better shape is the one I used in SPIFFE for …
Read more →An agentic mesh is infrastructure that applies identity, policy, and observability to agent traffic (calls to models, tools, and other agents) so those controls …
Read more →An OpenAI research agent got its HTTPS requests to a public chatbot blocked by a web proxy. So it found a different way to ask the chatbot questions: it queried …
Read more →Disclosure: I work at Solo.io, which created agentgateway and sells Solo Enterprise for agentgateway. Every product claim below links to that project’s …
Read more →Every capacity knob in an agent runtime today is an efficiency knob. Pack more agents onto fewer pods, snapshot the idle ones, scale the pool to match demand, …
Read more →An AI agent that stops calling its tools does not throw an error. It answers from the model’s memory, confidently and plausibly, and the output still …
Read more →Agents parse HTML badly and expensively. The usual fix is to make the site emit markdown: add a per-page index.md, publish an llms.txt, change the build. That …
Read more →Two things get asked for the moment agents start doing real work. Stop it now, and keep everything it did. Those usually fight. The natural place to log what an …
Read more →Updated 2026-10-30: the current docs replace AgentInstance with Harness + AgentTemplate + Agent, with conversations as Sessions. The next section has the …
Read more →An AI agent that calls a model, a tool, or another agent has to prove who it is. Almost every production failure I have written up this month traces back to …
Read more →Almost everything in this series started the same way: a control that everybody agrees is the right control, applied to an agent, quietly not doing the thing …
Read more →I gave an agent pod an LLM API key the normal way, as a Secret projected into its environment. Then I turned on every Kubernetes control that sounds like it …
Read more →Solo shipped agentgateway enterprise 2026.9.0 on Tuesday, and the part worth your attention is not a feature inside the proxy. It is where the token service now …
Read more →kagent v0.10.0 went GA on September 4. Buried in a long release list is a pair of environment variables that decide whether an agent’s credential works at …
Read more →An autonomous agent escaped its evaluation sandbox on July 9, 2026, and about twelve and a half hours of wall-clock work later it held cluster-admin on multiple …
Read more →Three companies authenticate against three different identity providers, connect to the same three MCP URLs, and get three completely different products. Acme …
Read more →I open-sourced Substrate Scope, a live visualizer for Agent Substrate, the Kubernetes-native runtime that runs AI agents as snapshot-backed actors in gVisor …
Read more →Agent Substrate is a Kubernetes-native runtime that breaks the pod-per-agent model. It is one of the runtimes that sit under an agentic mesh. Instead of one …
Read more →Cap LLM spend at the AI gateway: give each team or agent a virtual key, price every request against a model catalog, and refuse the request with HTTP 429 once …
Read more →Originally posted on DZone Hey internet humans! I’ve recently re-entered the world of observability and monitoring after a short detour in the Internal …
Read more →Kubernetes administration is like navigating through a perpetually expanding puzzle, where distinguishing essential components from duplicate information …
Read more →Getting comprehensive visibility into a Kubernetes cluster requires gathering data across multiple layers. This involves collecting information about nodes, …
Read more →