Gateway API
The successor to Ingress: role-separated resources (GatewayClass, Gateway, HTTPRoute) where infrastructure teams own listeners and app teams attach routes, with header matching, traffic splitting, and cross-namespace references as first-class typed fields instead of annotations. GA and the current recommended API for new L7 routing.
This Concept is waiting for its first lesson!
The successor to Ingress: role-separated resources (GatewayClass, Gateway, HTTPRoute) where infrastructure teams own listeners and app teams attach routes, with header matching, traffic splitting, and cross-namespace references as first-class typed fields instead of annotations. GA and the current recommended API for new L7 routing.
Are you a teacher? Sign in to start contributing.
Sign In