Envoy Gateway
Envoy Gateway is the primary traffic entry point for new workloads in Edka. It implements Gateway API and gives you a managed way to expose services with public or private load balancers, custom domains, and gateway level traffic controls.
- Managed Gateway API entry points for Kubernetes workloads
- Public and private Gateway classes backed by dedicated load balancers
- Integration with wildcard and hostname domains and cert-manager for TLS
- Gateway-class request timeout defaults for long-running HTTP requests
- Aggregate traffic metrics for requests, latency, 5xx, and active connections
Features available
Edka’s Envoy Gateway integration is managed from the cluster Gateway tab. From there you can install the controller, create additional Gateway classes, set request timeout defaults, review primary endpoints, and monitor aggregate traffic without manually wiring load balancers or controller settings.
Envoy Gateway is the standard traffic entry point in Edka. NGINX Ingress is deprecated; existing installs should migrate to Gateway API.
Deploy Envoy Gateway
Envoy Gateway
Networking
Run Gateway API on Kubernetes with managed Envoy Gateway classes, public and private entry points, and gateway level traffic observability.