openyurtio/openyurt

English | 简体中文

| What is NEW! | |-----------------------------------------------------------------------------------------------------------| | Latest Release: Jan 7th, 2025. OpenYurt v1.6.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 Incubating 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.

Architecture

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 serves as a node sidecar to handle requests that come from components (like Kubelet, Kubeproxy, etc.) on worker nodes to kube-apiserver.
• Yurt-Manager: includes all controllers and webhooks for edge.
• Raven-Agent: 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 in a vanilla Kubernetes cluster.
• YurtIoTDock: One instance of YurtIoTDock is deployed in every edge NodePool, for bridging EdgeX Foundry platform and uses Kubernetes CRD to manage edge devices.

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.

Getting started

OpenYurt is currently certified to support up to Kubernetes version 1.30. Compatibility with subsequent versions of Kubernetes is expected, but has not yet been verified. OpenYurt installation is divided into two parts:

• Install OpenYurt Control Plane Components
• Join Nodes

Roadmap

• OpenYurt Roadmap

Community

Contributing

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.

Contact

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)

License

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.