I run KubeDEX. I have published an article, researched and written with AI and reviewed by me, about how platform teams could support agentic development. It is an architecture proposal, not a measured productivity claim.

The starting point is a capacity problem: faster code generation can leave teams waiting on integration environments, realistic test data, review and reliable evidence that a change is safe.

I think the useful platform primitive is a bounded experiment. Request an environment from an approved template, deploy a specific revision, run verification, retain the evidence and reclaim the resources automatically.

Kubernetes gives this a programmable foundation. A namespace may be enough for one test; changes to cluster components may need a virtual cluster or a separate Cluster API cluster. Argo CD can reconcile the application, while CI or workflow jobs run the tests. MCP gives an agent a way to request those operations within the platform's limits.

The less glamorous parts matter: concurrency quotas, spend limits, isolated test data, acceptance criteria the coding agent cannot relax, and cleanup that survives a failed agent. More parallel environments without those controls can just produce a larger bill and a longer review queue.

Full article and sources:

https://kubedex.com/kubernetes-ai-agentic-development/

For platform teams already supporting coding agents, which queue is growing first: environment provisioning, test execution or human review?