Kubernetes note people miss:
AgentgatewayModel is experimental and off by default.
Higher-level than hand-wiring backends + HTTPRoutes. Existing APIs stay.
Upgrade first. Pilot one non-prod model second.
I matched my agentgateway 1.4.0 write-up to the official release notes.
Not just features — breaking changes + a High severity MCP auth advisory too.
If you skimmed 1.4 as “nice UI stuff,” read this thread.
Full post + UI Settings screenshot:
maniak.io/articles/2026-…
On 1.3? Start here: convert binds → gateways, protect the UI, try one AgentgatewayModel, then fix one upstream still using a god-mode SA.
A few upgrade notes so nobody gets surprised:
• bump CRDs before controller/proxy
• standalone chart/values changed — read them
• musl images are gone
• DaemonSet gateways exist if you need node-local
Blind helm upgrade is a bad idea on this one.
agentgateway 1.4.0 shipped today.
I went through everything between 1.3.0 and 1.4.0 and wrote up what actually matters if you run this in the real world — not every PR, just the stuff that changes day-2 ops.
🧵
Join me this week on a webinar where I dive into building agents in production. solo.io/resources/webi…
I will dive into graph engineering, tokemaxxing and accessing that solo and Google are building with agent substrates.