emissary-ingress/emissary

open source Kubernetes-native API gateway for microservices built on the Envoy Proxy

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 16 minutes ago
Added to GitGenius on September 15th, 2026
Created on March 30th, 2017
Open Issues & Pull Requests: 403 (+0)
GitHub issues: Enabled
Number of forks: 707
Total Stargazers: 4,522 (+0)
Total Subscribers: 75 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 11.8 days
Mean response time: 99.5 days
90th percentile: 240.8 days
Tracked items: 88

Most active contributors

Sign in to see contributor activity.

How this project is maintained

94% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 63% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 63
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 991 days
Stale 30+ days: 60
Stale 90+ days: 58

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • t:bug (40)
  • stale (30)
  • t:feature (29)
  • pinned (7)
  • contrib-fest (6)
  • needs-triage (4)
  • good first issue (3)
  • needs-design (3)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

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.