Envoy Gateway Controller

Attention

Envoy Gateway Controller takes the place of the NGINX Ingress Controller.

Available as of MKE 3.9.0 The Envoy Gateway Controller runs Envoy Gateway as the Kubernetes Gateway API implementation. It handles HTTP traffic entering the cluster from outside by applying Gateway, HTTPRoute, and other related resources. You can route requests using hostnames and URL paths to the appropriate services in your cluster.

Only cluster administrators can enable or disable the Envoy Gateway Controller. Administrators and other users with the appropriate Kubernetes roles and grants can create and manage Gateway API resources in the namespaces where they are permitted.

You can define Envoy Gateway Controller settings through the cluster_config.gateway_controller section of the MKE configuration file or from the Admin Settings > Gateway page in the MKE web UI.

The following table details the default Envoy Gateway API names:

Resource

Value

GatewayClass

envoy-gatewayingress

Controller name

gateway.envoyproxy.io/mke-gatewayclass-controller