Envoy Gateway lets teams describe incoming application traffic with Kubernetes Gateway API resources and have Envoy proxies carry out those rules. It supplies the controller that watches the declarations and configures the traffic-handling proxies. This is useful when you want a Kubernetes gateway without building that configuration machinery around Envoy yourself. The supported routes and policies still depend on the selected release, especially when replacing behavior expressed through another controller's annotations.
Fit for an ingress migration
Map required routing, authentication, timeout, rate-limit and TLS behavior to documented features in the selected release. Standard Gateway API resources and implementation-specific policies need separate review. A controller's conformance record does not certify every annotation from ingress-nginx.
Operational boundaries
Assign GatewayClass, gateway, route, certificate and CRD ownership. Confirm that installing the chart will not overwrite a Gateway API bundle managed by another platform component. Test a denied route attachment and an unavailable backend in addition to normal traffic.
Use the ingress-nginx migration plan to build a request matrix and preserve a reversible traffic path during cutover.
Sources & further reading
Spotted something that needs another look?
Help improve this page →