In the news
Agents are sessions, not requests: size GKE node pools for AI agent sessions- Google Developers Blog
Google Developers · Published · 3 min read
In 30 seconds
- What happened
- Google released Agent Substrate 1.0 on GKE, enabling agent sessions to park in object storage while idle, freeing compute resources between prompts.
- Why it matters
- Teams running coding agents on shared GKE clusters need this to reduce node costs when agents wait between user prompts throughout the workday.
- Watch out
- Parking saves costs only below roughly 4.5 prompts per hour; at higher prompt rates, keeping one Pod per session becomes cheaper. Control plane costs require at least 37 sessions to break even.
- agent
The patterns behind this
Each one covers how the technique works, when it earns its cost, and where it breaks.
The Agent Architect
One pattern, one tradeoff, one production failure story. A short weekly briefing for people building agentic systems.
Weekly email, one-click unsubscribe. We only use your address to send the briefing.