Back to Add-ons

NGINX Ingress (Deprecated)

NGINX Ingress is deprecated in Edka and is being phased out. New clusters and new workloads should use Envoy Gateway with Gateway API, which is the standard traffic management path going forward.

Existing NGINX Ingress installations continue to run for now, but we recommend migrating to Gateway API. NGINX Ingress is no longer recommended for new deployments and will be removed in a future release.

Migrating to Gateway API

Gateway API with Envoy Gateway covers the same routing, TLS, and load-balancing needs with a Kubernetes-native API and managed public and private Gateway classes:

  1. HTTP/HTTPS routing with host and path rules through Gateway and HTTPRoute resources
  2. TLS termination with cert-manager for automatic certificate management
  3. Public and private Gateway classes backed by dedicated load balancers
  4. Gateway-level traffic metrics for requests, latency, 5xx, and active connections

Switch to Envoy Gateway
icon related to NGINX Ingress

NGINX Ingress

Networking

Deprecated NGINX ingress controller, kept for migration. Edka now standardizes on the Gateway API with Envoy Gateway for routing, TLS, and traffic management.