emissary-ingress/emissary

Health v2 · maintenance only

Adoption not part of the score

4519 stars · 706 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded

Emissary-ingress is an open-source, Kubernetes-native API gateway, Layer 7 load balancer, and Kubernetes Ingress built on Envoy Proxy. It is a CNCF incubation project (formerly Ambassador API Gateway) configured declaratively via Kubernetes CRDs or annotations.

Use cases

• expose microservices behind a Kubernetes API gateway
• manage ingress traffic and load balancing for a Kubernetes cluster
• route gRPC, HTTP/2, TCP, and WebSocket traffic to services
• add authentication, rate limiting, and TLS to APIs
• run canary releases and progressive delivery
• integrate ingress with Istio, Linkerd, or Consul service meshes
• monitor API traffic with Prometheus, Grafana, or Datadog

When to choose

• you run microservices on Kubernetes and need a native, CRD-driven API gateway
• you want Envoy Proxy power with declarative self-service configuration
• you need ingress, auth, rate limiting, and canary delivery in one component
• you want a CNCF-governed open-source alternative to commercial API gateways

When to avoid

• you are not running Kubernetes or prefer a host-based gateway
• you need a lightweight sidecar-less proxy without cluster CRDs
• you require full API management features like developer portals or monetization
• your team cannot operate Envoy-based infrastructure

Facets

service · maturity stable

api-gateway routing rate-limiting auth load-testing middleware http-server monitoring microservices cloud-computing apis backend networking cloud self-hosted go python envoy-proxy ingress gateway-api cncf layer-7-load-balancing canary-releases service-mesh grpc tls observability devops containers kubernetes docker

Member repositories

For agents

markdown · JSON · MCP: product_card(name="emissary-ingress/emissary")