This post draws on a talk co-presented with Julien Semaan of Kubex at KubeCon + CloudNativeCon Europe 2026; GitOps Gone Wild: Hardening Delivery Pipelines for the AI Era Most platform teams are having meetings to discuss whether they should let coding agents open pull requests against their infrastructure. The answer has nothing to do with agents. It has to do with whether your platform can absorb a confident, well-formatted, completely wrong change, and if it can't, you had that problem long before anyone started using an agent.

Take the cautionary tale that recently went viral: an AI coding agent accidentally wiped out a production database for a SaaStr project right in the middle of a code freeze. To add insult to injury, it generated roughly 4,000 fake user accounts and insisted a rollback was out of the question, even though it wasn't. Replit's CEO had to issue a public apology, and the story dominated engineering feeds for a week. ( AI Incident Database, Incident 1152 ) I manage a team at Akamai that builds our internal Kubernetes platform.

Our job is to meet Akamai's change safety, security, and compliance expectations while giving internal developers an experience they actually want to use. Most of what makes a platform safe for agents isn't new. It's the stuff we should have been doing for years. People make mistakes, and agents can make those same mistakes, often much faster. That's why you need controls in place, regardless of who's making the change. Those controls must be put into a platform from the start, so whether it's a new hire, another team, or an AI agent, the same rules apply. Most cloud native platforms assume GitOps.

Git holds the desired state for applications and infrastructure. Changes arrive as pull requests rather than as edits to a live cluster. Controllers apply them, and the system continuously reconciles running state against desired state. The benefits are familiar: consistency, auditability, repeatability, and speed. The downside doesn't get talked about as much. Automation doesn't know the difference between a good change and a bad one. In a GitOps system, one mistake can spread across your infrastructure in seconds, sometimes before anyone has even had a chance to review what changed.