easegress-io/easegress

A Cloud Native traffic orchestration system. (CNCF Project)

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 21 minutes ago
Added to GitGenius on September 11th, 2026
Created on May 28th, 2021
Open Issues & Pull Requests: 10 (+0)
GitHub issues: Enabled
Number of forks: 498
Total Stargazers: 5,869 (+0)
Total Subscribers: 99 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

Easegress is a cloud-native traffic orchestration system designed to manage and route network traffic across distributed systems.

The tool addresses the challenge of coordinating complex traffic flows in microservice architectures by providing a unified platform for traffic orchestration. It uses a pipeline-based architecture where traffic flows through configurable filters that can be composed to implement routing, load balancing, rate limiting, and other traffic control policies. The system achieves high availability through built-in Raft consensus and leader election, and it emphasizes observability by exposing meaningful statistics about traffic and system behavior.

Easegress suits organizations running Kubernetes clusters or microservice deployments that need sophisticated traffic management beyond basic load balancing. It works well for teams building API gateways, service meshes, or reverse proxies where traffic policies need to be dynamically configured and updated. The tool's extensibility through custom filters and controllers makes it appropriate for projects with specialized traffic handling requirements. Its integration points with Kubernetes Ingress, sidecars, and workflow systems position it as a component within larger cloud-native stacks rather than a standalone solution.

Work in the issue tracker is dominated by questions and bug reports, with significant activity around version three development, indicating ongoing refinement of core functionality and active engagement with users seeking clarification on implementation details.