 What is NEW! |
|---|
| May 29th, 2020. OpenYurt v0.1.0 is RELEASED! Please check the CHANGELOG for details. |
OpenYurt is built based on native Kubernetes and targets to extend it to support edge computing seamlessly. In a nutshell, OpenYurt enables users to manage applications that run in the edge infrastructure as if they were running in the cloud infrastructure.
OpenYurt is suitable for common edge computing use cases whose requirements include:
- minimizing the network traffic over long distances between the devices and the workloads.
- overcoming the network bandwidth or reliability limitations.
- processing data remotely to reduce latency.
- providing a better security model to handle sensitive data.
OpenYurt has the following advantages in terms of compatibility and usability.
- Kubernetes native. It provides full Kubernetes API compatibility. All Kubernetes workloads, services, operators, CNI plugins, and CSI plugins are supported.
- Seamless conversion. It provides a tool to easily convert a native Kubernative to be "edge" ready. The extra resource and maintenance costs of the OpenYurt components are very low.
- Node autonomy. It provides mechanisms to tolerate unstable or disconnected cloud-edge networking. The applications run in the edge nodes are not affected even if the nodes are offline.
- Cloud platform agnostic. OpenYurt can be easily deployed in any public cloud Kubernetes services.
As shown in the figure, OpenYurt follows a classic edge application architecture design -
a centralized Kubernetes master resides in the cloud site, which
manages multiple edge nodes reside in the edge site. Each edge node has moderate compute resources allowing
running a number of edge applications plus the Kubernetes node daemons. The edge nodes in a cluster can span
multiple physical regions. The terms region and unit are interchangeable in OpenYurt.
The major OpenYurt components consist of:
- YurtHub: A node daemon that serves as a proxy for the outbound traffic from the Kubernetes node daemons (Kubelet, Kubeproxy, CNI plugins and so on). It caches the states of all the resources that the Kubernetes node daemons might access in the edge node's local storage. In case the edge node is offline, those daemons can recover the states upon node restarts.
- Yurt controller manager: It manages a few controllers such as
the node controller and the unit controller (not released yet) for different edge computing use cases. For example,
the Pods in the nodes that are in the
autonomymode will not be evicted from APIServer even if the node heartbeats are missing. - Yurt tunnel server: It connects with the
YurtTunneldaemon running in each edge node via a reverse proxy to establish a secure network access between the cloud site control plane and the edge nodes that are connected to the intranet.
OpenYurt supports Kubernetes versions from 1.12 to 1.14. Please make sure your Kubernetes cluster version is within the supported version range to avoid any compatibility issues. We will support higher Kubernetes versions shortly.
You can convert an existing Kubernetes cluster to a yurt cluster manually or using command line tool yurtctl
It is recommended that you install OpenYurt components via yurtctl. You can iterally install everything in one cmd line.
You can get yurtctl by building the binary using the following command
make WHAT=cmd/yurtctl
After compiling, you can convert a Kubernetes cluster into a Yurt cluster by typing command
# assume that the target cluster is a one-node minikube cluster
_output/bin/yurtctl convert --provider minikubeFor further details regarding yurtctl, please refer to yurtctl tutorial
We provider a detailed tutorial to demonstrate how to use OpenYurt to manage edge applications.
There's a Makefile in the root folder which describes the options to build and install. Here are some common ones:
If you have any questions or want to contribute, you are welcome to communicate most things via GitHub issues or pull requests.
Other active communication channels:
- Mailing List: TODO
- Dingtalk Group(钉钉讨论群)
Certain implementations in OpenYurt rely on the existing code from Kubernetes and the credits go to the original Kubernetes authors.