openyurtio/raven

provide layer 3 and layer 7 network connectivity among pods in different physical regions

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓

openyurtio/raven has 60+ stars and 40+ forks on GitHub, is written in Go, and was last pushed on Oct 12, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 49 minutes ago
Added to GitGenius on October 15th, 2026
Created on December 10th, 2021
Open Issues & Pull Requests: 25 (+0)
GitHub issues: Enabled
Number of forks: 44
Total Stargazers: 66 (+0)
Total Subscribers: 7 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 22.1 days
Mean response time: 371.1 days
90th percentile: 995.2 days
Tracked items: 12

Maintainer activity

1 person did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 4
New in 7 days: 0
Closed in 7 days: 1
Avg open age: 1,112 days
Stale 30+ days: 4
Stale 90+ days: 2

Recent activity

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

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Raven is a Kubernetes networking component that provides layer 3 and layer 7 network connectivity among pods across different physical regions.

Raven addresses the challenge of enabling seamless pod-to-pod communication in edge computing environments where clusters span multiple physical locations. The problem arises in edge-cloud and edge-edge scenarios where standard Kubernetes networking assumes all nodes are in a single region. Raven solves this by introducing a controller-agent architecture: a Raven Controller Manager acts as a standard Kubernetes controller that elects gateway nodes for each edge region based on node conditions, while Raven Agent runs as a node daemon that dynamically configures routing information and VPN connections on each node according to its role, whether as a normal node or gateway node.

Raven is designed for organizations running OpenYurt clusters that need to connect pods across geographically distributed edge locations and cloud infrastructure. It suits projects where edge nodes are separated by network boundaries that prevent direct pod-to-pod communication, and where treating the entire distributed infrastructure as a single logical cluster is desirable. The tool is specifically built as a component of OpenYurt rather than as a standalone solution, so adoption assumes an OpenYurt deployment.

The project maintains active communication channels including a mailing list, Slack workspace, and Dingtalk group for community engagement. The repository includes a tutorial documenting how to get started with Raven Agent and welcomes contributions through issues and pull requests, with a dedicated contributing document provided for potential contributors.