kubeedge/edgemesh

Simplified network and services for edge applications

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓

kubeedge/edgemesh has 250+ stars and 100+ forks on GitHub, is written in Go, and was last pushed on Apr 10, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 13 minutes ago
Added to GitGenius on October 15th, 2026
Created on May 12th, 2021
Open Issues & Pull Requests: 61 (+0)
GitHub issues: Enabled
Number of forks: 146
Total Stargazers: 293 (+0)
Total Subscribers: 6 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.8 hours
Mean response time: 37.1 days
90th percentile: 107.9 days
Tracked items: 14

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 12
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 740 days
Stale 30+ days: 12
Stale 90+ days: 11

Recent activity

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

Top labels

  • kind/bug (11)
  • kind/feature (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

EdgeMesh is a data plane component for Kubernetes edge clusters that provides service discovery and traffic proxy functions for applications running across distributed edge nodes.

EdgeMesh addresses the challenge of service communication in edge computing environments where network topology is complex, nodes may be geographically dispersed and disconnected, and resources are constrained. It uses LibP2P to establish connections between edge nodes, distinguishing between intra-LAN communication (direct access) and cross-LAN communication (which attempts hole punching for direct tunnels or falls back to relay forwarding). Service metadata is distributed through the KubeEdge edgehub/cloudhub tunnel rather than requiring access to a cloud API server, and the tool includes a lightweight node-level DNS server for service discovery. Each edge node runs a single Agent, minimizing resource consumption.

EdgeMesh is designed for deployments using KubeEdge where applications need to communicate across edge nodes in different locations without relying on cloud infrastructure for every transaction. It suits scenarios with limited edge resources, unstable edge-to-cloud connectivity, or complex network structures. Compared to the traditional Kubernetes approach of CoreDNS plus Kube-Proxy plus CNI plugins, EdgeMesh simplifies deployment to a single Agent per node while enabling edge-to-edge, edge-to-cloud, and cloud-to-edge communication across different LANs.

The project shows consistent development activity with regular commits and pull request reviews. Maintenance includes active issue triage and response to user questions. The codebase receives updates addressing both bug fixes and feature enhancements. Documentation is maintained in multiple languages to support a broader user base.