NGINX Ingress Controller (Legacy)
NGINX Ingress Controller remains available in EDKA for workloads that still rely
on classic Kubernetes Ingress resources. For new clusters and new workloads,
EDKA recommends Envoy Gateway with Gateway API as the default traffic
management path.
- HTTP/HTTPS traffic routing with advanced path-based rules and host-based virtual servers
- TLS termination and integration with cert-manager for automatic certificate management
- Load balancing with multiple algorithms (round-robin, least connections, IP hash)
- Rate limiting, rewriting, and advanced traffic management capabilities
Features available
EDKA’s NGINX Ingress implementation includes pre-configured security headers, customizable timeout settings, and WebSocket support. Use it when you need compatibility with existing ingress manifests or third-party charts that have not yet adopted Gateway API.
Deploy NGINX Ingress
Nginx Ingress
Networking
Legacy ingress controller support for Kubernetes workloads that still rely on classic Ingress resources.