English | 简体中文
 What is NEW! |
|---|
| Latest Release: Jan 19th, 2023. OpenYurt v1.2.0. Please check the CHANGELOG for details. |
| First Release: May 29th, 2020. OpenYurt v0.1.0-beta.1 |
OpenYurt is built based on upstream Kubernetes and now hosted by the Cloud Native Computing Foundation(CNCF) as a Sandbox Level Project.
OpenYurt has been designed to meet various DevOps requirements against typical edge infrastructures. It provides consistent user experience for managing the edge applications as if they were running in the cloud infrastructure. It addresses specific challenges for cloud-edge orchestration in Kubernetes such as unreliable or disconnected cloud-edge networking, edge autonomy, edge device management, region-aware deployment and so on. OpenYurt preserves intact Kubernetes API compatibility, is vendor agnostic, and more importantly, is SIMPLE to use.
OpenYurt follows a classic cloud-edge architecture design.
It uses a centralized Kubernetes control plane residing in the cloud site to
manage multiple edge nodes residing in the edge sites. Each edge node has moderate compute resources available in order to
run edge applications plus the required OpenYurt components. The edge nodes in a cluster can span
multiple physical regions, which are referred to as Pools in OpenYurt.
The above figure demonstrates the core OpenYurt architecture. The major components consist of:
- YurtHub: YurtHub runs on worker nodes as static pod and serve as a node sidecar to handle requests that comes from components(like Kubelet, Kubeproxy, etc.) on worker nodes to kube-apiserver.
- Yurt Controller Manager: It includes several controllers for edge control loops.
yurtcsrapprovercontroller is used for handling CSRs from OpenYurt components.daemonpodupdatercontroller is used for providing OTA and Auto upgrade model for DaemonSet workload.servicetopologycontroller is used for reconciling endpoints/endpointslices when service or nodepool happen to change.poolcoordinatorcontroller mainly works with the Pool-Coordinator component to provide users with the ability of edge autonomy (including two modes of node autonomy and node pool autonomy).
- Yurt App Manager: It manages several CRD resources introduced in OpenYurt: NodePool,
YurtAppSet, YurtAppDaemon
and YurtIngress.
NodePoolprovides a convenient management for a pool of nodes within the same region or site.YurtAppSetdefines a new edge application management methodology of using per NodePool workload.YurtAppDaemonenables to deploy workload for every matching NodePool.YurtIngressorchestrates the deployment of multiple ingress controllers to the respective NodePools.
- Raven/Raven Controller Manager: It is focused on edge-edge and edge-cloud communication in OpenYurt, and provides layer 3 network connectivity among pods in different physical regions, as there are in one vanilla Kubernetes cluster.
- Pool-Coordinator: One instance of Pool-Coordinator is deployed in every edge NodePool, and in conjunction with YurtHub to provide heartbeat delegation, cloud-edge traffic multiplexing abilities, etc.
In addition, OpenYurt also includes auxiliary controllers for integration and customization purposes.
- Node resource manager: It manages additional edge node resources such as LVM, QuotaPath and Persistent Memory. Please refer to node-resource-manager repo for more details.
- Integrating EdgeX Foundry platform and uses Kubernetes CRD to manage edge devices!
| OpenYurt introduces Yurt-edgex-manager to manage the lifecycle of the EdgeX Foundry software suite, and Yurt-device-controller to manage edge devices hosted by EdgeX Foundry via Kubernetes custom resources. Please refer to the short demo and the respective repos for more details. | 
|
Please check the resource and system requirements before installing OpenYurt.
OpenYurt supports Kubernetes versions up to 1.23. Using higher Kubernetes versions may cause compatibility issues. OpenYurt installation is divided into two parts:
To experience the power of OpenYurt, please try the detailed tutorials.
If you are willing to be a contributor for the OpenYurt project, please refer to our CONTRIBUTING document for details. We have also prepared a developer guide to help the code contributors.
| Item | Value |
|---|---|
| APAC Friendly Community meeting | Adjust to weekly APAC (Starting May 11, 2022), Wednesday 11:00AM GMT+8 |
| Meeting link APAC Friendly meeting | https://us02web.zoom.us/j/82828315928?pwd=SVVxek01T2Z0SVYraktCcDV4RmZlUT09 |
| Meeting notes | Notes and agenda |
| Meeting recordings | OpenYurt bilibili Channel |
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: https://groups.google.com/g/openyurt/
- Slack: OpenYurt channel (English)
- DingTalk：Search GroupID
12640034121(Chinese)
OpenYurt is under the Apache 2.0 license. See the LICENSE file for details. Certain implementations in OpenYurt rely on the existing code from Kubernetes and the credits go to the original Kubernetes authors.