Raven
1. Background
In edge computing, edge-edge and edge-cloud are common network communication scenarios. In OpenYurt, we have introduced YurtTunnel to deal with the network problems of maintenance and monitoring in edge-cloud collaboration, providing the capability of kubectl exec/logs on edge nodes and collecting monitoring indicators from edge nodes. But the problems solved by YurtTunnel are only a part of edge-cloud communication. We also need to provide solutions for edge-edge and edge-cloud container network communication.
In OpenYurt cluster, pods in different physical regions may need to use Pod IP, Service IP or Service name to communicate with other Pods. Although these pods are in a single K8s cluster, they are in different physical regions (network domains) and cannot communicate directly. So we create Raven project to solve this problem.
2. Architecture
As following picture, the architecture of Raven have two components:
-
Raven Controller Manager：The native Kubernetes controller is deployed in some nodes on the cloud as a
Deployment, monitoring the status of edge nodes, selecting an egress for cross-edge traffic as a gateway node for each edge node pool. When the current gateway node is dead and other node will be switched. All cross-edge traffic will be forwarded by the gateway node of each edge node pool; -
Raven Agent：It is deployed as a
DaemonSetand runs on each node of the K8s cluster. It configures route or VPN tunnel on the node according to the role of each node (gateway or non-gateway);
The above two components are connected by a Gateway CRD to exchange routes and VPN tunnels, as shown in the following picture:
For more details, please refer to the code repository of the Raven project:
3. Features and Advantages
Features:
- No intrusion: No intrusion into the native K8s CNI network, only cross-edge traffic is hijacked for forwarding
- Security: Use stable
IPsecto encrypt cross-edge traffic
Advantages:
Ravenwill try to use the network capabilities of the edge itself, create edge-to-edge VPN tunnels as possible, and will not forward all cross-edge traffic through the cloud centerRavendoes not hijack the traffic in the same edge node pool, and keeps the CNI capabilities of the cluster itself
4. Version
Raven Controller Manager:
| version | image | release | content | comment |
|---|---|---|---|---|
| v0.1.0 | openyurt/raven-controller-manager:v0.1.0 | 2022.05 | first | support Gateway Node election |
| v0.2.0 | openyurt/raven-controller-manager:v0.2.0 | 2022.12 | feature | support multi Pod CIDRs support Calico |
| v0.3.0 | openyurt/raven-controller-manager:v0.3.0 | 2023.1 | feature | support node IP forwarding |
Raven Agent：
| version | image | release | content | comment |
|---|---|---|---|---|
| v0.1.0 | openyurt/raven-agent:v0.1.0 | 2022.05 | first | Support IPsec as VPN backend, which implemented by using libreswan |
| v0.2.0 | openyurt/raven-agent:v0.2.0 | 2022.12 | feature | Support WireGuard as VPN backend Support Calico |
| v0.3.0 | openyurt/raven-agent:v0.3.0 | 2023.1 | feature | Support node IP forwarding |
5. future plan
- Support SLB as public network exporter for gateway 【issue #22】
- Support NAT traversal 【issue #13】
- Support distribute route path decision 【issue #14】
- route path cost evaluation
- shortest path decision
- keep networking connection alive during paths change
Welcome interested students to join us and contribute code!!