What is Emissary-Ingress?
open source Kubernetes-native API gateway for microservices built on the Envoy Proxy. It is a CNCF incubating project in api gateway.
- Use case
- Emissary-Ingress is a k8s-native, Envoy-based API gateway. It is designed to allow teams to work in a more decentralized way than the traditional Ingress object. Emissary-Ingress can scan for its CRDs across all namespaces, so development teams can deploy new network routing rules along with the apps that use them, increasing velocity. Emissary-Ingress can be extended via API calls with authentication and rate limiting services. It is compatible with all the CNCF service meshes, and facilitates canary deployments when integrated with Argo Rollouts.
- For
- Platform Engineers, Architects
- Tags
- ingress · api gateway · gateway · decentralized-operation · developer-friendly
- Releases
- Monthly
- Licence
- Apache License 2.0 · Python, Go
Stars and activity
Star history: daily readings started on 21 Nov 2026; the chart appears after a few days.
Commits each week, the last 52 weeks
Maintainers
3 maintainers, from CNCF's maintainers list · companies include Buoyant, Inc., Evil Geniuses For A Better Tomorrow, ActiveCampaign
- - FlynnBuoyant, Inc. · @kflynn
- Mark S.Evil Geniuses For A Better Tomorrow · @the-wondersmith
- Phil PebleActiveCampaign · @ppeble
Emissary-Ingress FAQ
Is Emissary-Ingress a CNCF incubating project?
Yes. Emissary-Ingress is a CNCF incubating project, since 13 Apr 2021.
Is there a Emissary-Ingress certification?
Not yet. CNCF certifications cover Kubernetes and a growing list of projects.
How many GitHub stars does Emissary-Ingress have?
4,524 on 21 Nov 2026.
What are the alternatives to Emissary-Ingress?
Other CNCF api gateway projects: Higress, Easegress, Kgateway, Kuadrant.




