Gateway API (Envoy Gateway)
Kubernetes Gateway API ingress controller powered by Envoy Gateway.
Component Category
Networking / ingress and routing
Component Description
Gateway API is the Kubernetes-native ingress standard that replaces the older Ingress resource model. In the platform, it is deployed via Envoy Gateway, which implements the Gateway API specification using Envoy proxy as the data plane. The component manages a shared Gateway resource and per-component HTTPRoute resources for traffic routing.
Why It Is Used
In BullSequana AI, Gateway API provides the primary ingress path for all platform endpoints. It replaces the legacy NGINX ingress controller with a standards-based routing model that supports advanced traffic policies, header-based routing, and native TLS termination through the Kubernetes Gateway API specification.
Learn More
Deployment notes
Gateway API deploys at sync wave 4 (early infrastructure). It creates a GatewayClass, a shared Gateway resource, and an EnvoyProxy configuration. Individual components define their own HTTPRoute resources to register their endpoints with the gateway.
The ingress-nginx component is retained in the platform but disabled by default. Gateway API is the active replacement.
Interacts With
cert-manager, which provisions TLS certificates referenced by the Gateway resource.External DNS, which creates DNS records for endpoints exposed through the gateway.All platform components, which define HTTPRoute resources to route traffic through the shared gateway.