Gateway API is what Ingress should have been from day one. I don’t say that lightly. I’ve spent years wrangling Kubernetes Ingress resources, writing controller-specific annotations, and debugging routing issues that only existed because the Ingress spec was too simple for real-world traffic management. Gateway API fixes nearly every complaint I’ve ever had, and if you’re still running pure Ingress in production, it’s time to start planning your migration. This isn’t a “maybe someday” technology. Gateway API hit GA in Kubernetes 1.26, major controllers already support it, and the ecosystem is moving fast. I’ve migrated three production clusters over the past year and I’m not looking back.
No comments yet. Log in to reply on the Fediverse. Comments will appear here.