envoyproxy/gateway

Manages Envoy Proxy as a Standalone or Kubernetes-based Application Gateway

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 22 minutes ago
Added to GitGenius on July 13th, 2023
Created on April 11th, 2022
Open Issues & Pull Requests: 758 (+0)
Number of forks: 843
Total Stargazers: 2,975 (+0)
Total Subscribers: 50 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 10.7 hours
Mean response time: 33.3 days
90th percentile: 75.3 days
Tracked items: 2,163

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 87% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "kind/bug" is answered fastest, typically in about 7 hours, while "area/policy" waits about 5 weeks. 44% of tracked open issues have had no activity in three months. Only 4% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 649
New in 7 days: 13
Closed in 7 days: 3
Avg open age: 305 days
Stale 30+ days: 496
Stale 90+ days: 416

Recent activity

Opened in 7 days: 11
Closed in 7 days: 3
Comments in 7 days: 24
Events in 7 days: 84

Top labels

  • triage (828)
  • stale (645)
  • help wanted (575)
  • kind/bug (521)
  • kind/enhancement (378)
  • documentation (319)
  • area/api (238)
  • area/testing (129)

Detailed Description

Envoy Gateway is an open source project that manages Envoy Proxy as either a standalone application or within Kubernetes environments. Written in Go, it leverages Gateway API resources to dynamically provision and configure managed Envoy Proxies, providing a modern approach to application gateway management in cloud-native infrastructure.

The project is classified across multiple domains including API gateway functionality, networking, service mesh integration, load balancing, proxy architecture, traffic management, observability, security policies, TLS termination, and policy enforcement. This broad classification reflects the comprehensive nature of the gateway solution, which handles routing, middleware, and security concerns alongside core proxy operations.

The repository demonstrates significant community engagement and activity.

This concentrated activity pattern indicates strong project leadership while the help wanted label prevalence suggests the project actively seeks additional contributors.

These connections indicate cross-pollination with other infrastructure and gateway projects in the ecosystem.

Envoy Gateway is positioned as a CNCF-related project, as evidenced by its topic tags and community structure. The project provides comprehensive documentation including a quickstart guide, compatibility matrix, and detailed roadmap. Community engagement is facilitated through multiple channels including dedicated mailing lists, Slack workspace integration, and regular contributor meetings held on alternating schedules to accommodate both EU and APAC time zones.

The project emphasizes security and proper contribution practices through documented security reporting procedures, a code of conduct, and detailed contributing and developer guides. Regular community meetings held on Thursdays at alternating times demonstrate commitment to inclusive participation across global time zones, with full meeting notes and agendas maintained for transparency.

As a Gateway API-compliant solution, Envoy Gateway enables dynamic configuration of Envoy Proxies through Kubernetes-native resources, making it suitable for organizations seeking to standardize on Envoy while maintaining compatibility with Kubernetes-native gateway patterns. The project's active triage and help wanted labels indicate ongoing development and a welcoming stance toward new contributors seeking to participate in gateway infrastructure development.