Ingress

Traffic that originates outside of your cluster, ingress traffic, is managed through the use of an ingress controller.

For new MKE 4 deployments, the only supported ingress solution is the Kubernetes Gateway API implemented with the Envoy Gateway controller, which MKE 4 offers by default starting with version 4.1.3. If, though, you are upgrading from MKE 3 or from an MKE 4 version earlier than 4.1.3, you can continue to use the Kubernetes Ingress API object with the NGINX Ingress Controller after upgrading to MKE 4.1.3—provided these components were enabled prior to the upgrade.