What’s New in OpenYurt v1.0? Key Updates and Future Roadmap

OpenYurt v1.0 Release Overview

OpenYurt, a cloud‑native edge infrastructure for cloud‑edge collaboration, reached its v1.0 release after more than two years of development. The release focuses on improving code quality, lowering entry barriers, enhancing core component performance, and unifying API governance.

ControlPlane SIG – Key Updates

API governance: NodePool resource upgraded to v1beta1 and all OpenYurt APIs migrated to the openyurtio/api repository (https://github.com/openyurtio/api).

Test coverage: Integrated CodeCov to track unit‑test coverage; most ControlPlane projects now reach ~50% coverage, with added E2E and fuzz tests for yurt‑app‑manager.

Performance testing: Focused on Yurthub component performance and pod recovery efficiency during node restarts; reports are available in the Yurthub performance test report (https://openyurt.io/docs/test-report/yurthub-performance-test and https://openyurt.io/docs/test-report/pod-recover-efficiency-test).

Installation optimization: Removed early K8s↔OpenYurt conversion tools and simplified installation to the OpenYurt Control‑Plane component (see installation summary at https://openyurt.io/docs/installation/summary).

Future Plans for ControlPlane

Node‑pool‑based operational monitoring to maintain visibility during cloud‑edge network disconnections (issue #775).

Pod eviction policies scoped to node pools for better edge workload availability (issue #779).

Network traffic reuse to cut cloud‑edge control traffic and reduce >95% of list/watch requests (issue #778).

Support OTA and auto upgrades for DaemonSet workloads (issue #914).

Rework yurtadm join command based on kubeadm (issue #889).

Improve service‑topology handling when Service or NodePool changes (issue #871).

Enhance image packaging workflow using Sealer (issue #942).

DataPlane SIG – Key Updates

Raven now supports WireGuard VPN backend, offering better performance than IPSec.

Raven adds Calico support, handling multi‑container network segments on single nodes.

Raven includes minimum MTU detection for network links.

Test coverage: CodeCov tracks unit‑test coverage for raven and raven‑controller‑manager, with coverage exceeding 60% for the DataPlane projects.

Future Plans for DataPlane

Expose Raven via SLB for public access, supporting cloud EIP or public IP for edge‑to‑edge and cloud‑edge networking (issue #22).

Enable NAT traversal to allow edge networks to communicate without cloud forwarding (issue #45).

Integrate Raven with yurt‑tunnel to unify network components (issues #40, #41).

IoT SIG – Key Updates

yurt‑edgex‑manager (renamed to yurt‑iot‑manager ) now supports Helm charts, Kubernetes 1.22+, EdgeX CRD webhooks, and improved Service types to avoid port conflicts.

yurt‑device‑controller adds bidirectional sync for device resources, upgrades Kube‑Builder, restructures project layout for multi‑group APIs, and fixes generation issues for EdgeX 2.x.

Test coverage: CodeCov tracks unit, E2E, and fuzz tests, raising IoT SIG coverage to ~45%.

Future Plans for IoT SIG (v0.3)

Rename manager to yurt‑iot‑manager, provide automated support for new EdgeX releases, and unify deployment of all IoT components.

Introduce a device‑management benchmark for OpenYurt.

Publish an end‑to‑end reference architecture combining OpenYurt, EdgeX, and OpenVINO for camera management and inference.