Emissary-ingress is a Kubernetes-native API gateway built on the Envoy Proxy that combines ingress traffic management, Layer 7 load balancing, and declarative routing configuration.
The tool addresses the need to manage microservices traffic with a unified control plane that integrates directly with Kubernetes. It works by accepting configuration through Kubernetes Custom Resource Definitions or service annotations, then translating that configuration into Envoy Proxy routing rules. This approach lets operators define traffic policies, authentication, rate limiting, and TLS termination declaratively alongside their Kubernetes resources, avoiding the need for separate configuration systems.
Teams should adopt Emissary-ingress if they run microservices on Kubernetes and want an ingress solution that supports advanced protocols like gRPC and HTTP/2, progressive delivery patterns such as canary releases, and integration with observability platforms like Prometheus and Grafana. It suits projects requiring sticky sessions, circuit breaking, and high availability features. The tool connects to service meshes including Consul, Linkerd, and Istio, and supports Knative serverless workloads. For organizations evaluating alternatives, the README does not name competing projects for direct comparison.
The project maintains active development on its main branch while keeping frozen branches for earlier versions. The original parent company has stepped back from direct involvement, placing greater emphasis on community-driven development and contributions going forward.