Skip to content
This repository has been archived by the owner on May 31, 2023. It is now read-only.

Latest commit

 

History

History
88 lines (52 loc) · 4.21 KB

CHANGELOG-1.12.md

File metadata and controls

88 lines (52 loc) · 4.21 KB

v1.12.0

Downloads for v1.12.0

Download v1.12.0 in the v1.12.0 release page.

KubeEdge v1.12 Release Notes

1.12 What's New

Introducing Alpha Implementation of Next-gen Cloud Native Device Management Interface(DMI)

DMI makes KubeEdge's IoT device management more pluggable and modular in Cloud Native way, which will cover Device Lifecycle Management, Device Operation, Device Data Management.

  • Device Lifecycle Management: Making IOT device's lifecycle management as easy as managing a pod with simplifies operations
  • Device Operation: Providing the ability to operate devices through Kubernetes API
  • Device Data Management: Separate from device management, the data can be consumed by local application or sync to cloud in special tunnel

Refer to the links for more details. (#4013, #3914)

Next-gen Edged Graduates to GA: Suitable for more scenarios

New version of the lightweight engine Edged, optimized from kubelet and integrated in edgecore, move to GA. New Edged will still communicate with the cloud through the reliable transmission tunnel.

Refer to the links for more details. (#4184)

Introducing High-Availability Mode for EdgeMesh

Compared with the previous centralized relay mode, EdgeMesh HA mode can set up multiple relay nodes. When some relay nodes break down, other relay nodes can continue to provide relay services, which avoids single point of failure and greatly improves system stability.

In addition, a relay node that is too far away will cause a high latency. The HA relay node capability can provide intermediate nodes to shorten the latency. The mDNS enables nodes in a LAN to communicate with each other without having to connect to an external network.

Refer to the links for more details. EdgeMesh#372

Support Edge Node Upgrade from Cloud

Introduce NodeUpgradeJob v1alpha1 API to upgrade edge nodes from cloud now. With NodeUpgradeJob API and Controller, users can:

  • Using NodeUpgradeJob API to upgrade selected edge nodes from cloud
  • If upgrade fails, rollback to the original version

Refer to the links for more details. (#4004, #3822)

Support Authorization for Edge Kube-API Endpoint

Authorization for Edge Kube-API Endpoint is now available. Third-party plugins and applications that depends on Kubernetes APIs on edge nodes must use bearer token to talk to kube-apiserver via https server in MetaServer.

Refer to the links for more details. (#4104, #4226)

New GigE Mapper

GigE Device Mapper with Golang implementation is provided, which is used to access GigE Vision protocol cameras.

Refer to the links for more details. (mappers-go#72)

Important Steps before Upgrading

  • If you want to upgrade KubeEdge to v1.12, the configuration file in EdgeCore has upgraded to v1alpha2, you must modify your configuration file of edged in EdgeCore to adapt the new edged.
  • If you want to use authorization for Edge Kube-API Endpoint, please enabled RequireAuthorization feature through feature gate both in CloudCore and EdgeCore. If RequireAuthorization feature is enabled, metaServer will only serve for https request.
  • If you want to upgrade edgemesh to v1.12, you do not need to deploy the existing edgemesh-server, and you need to configure relayNodes.
  • If you want to run EdgeMesh v1.12 on KubeEdge v1.12, and use https request to talk to KubeEdge, you must set kubeAPIConfig.metaServer.security.enable=true.