Gateway API Is the Direction. Your Controller Choice Is the Risk.

Gateway API Kubernetes adoption is settled. The project has made its call — GA in 1.31, role-based model, the ecosystem is moving. That decision is not the hard part. What isn't made — and what most guides skip entirely — is the controller decision that sits underneath it. Gateway API defines the routing model. It does not define what runs your traffic, how that component behaves under load, or what happens when it restarts in a cluster with five hundred routes and an incident already in progress. That's the controller decision. And it's where the architectural risk actually lives. This post covers what the controller decision actually hinges on: failure modes, Day-2 behavior, and the operational tradeoffs that don't appear in comparison matrices. Gateway API defines the model. Your controller choice determines the blast radius. Gateway API Kubernetes: Why the Controller Decision Matters Gateway API graduated to GA in Kubernetes 1.31. The role-based model — GatewayClass, Gateway, HTTPR