v1.0 What's New
This feature aims to support service mesh capabilities on the edge to support microservice communication cross cloud and edge. In v1.0.0 release, pod-to-pod communication on the same edge node or across
edge nodes in the same subnet is supported.
This feature enables edged to communicate with a CRI-compliant runtime to manage containers running on resource constrained edge nodes. Support for containerd is tested.
Quic protocol support
In order to enhance cloud and edge communication efficiency, communication between the edge and the cloud is now also supported via QUIC, a UDP-based protocol. CloudHub supports both Websocket and QUIC protocol access at the same time. The edgehub can choose one of the protocols to access the cloudhub.
Modbus Mapper is an application that is used to connect and control devices that use Modbus(RTU/TCP) as a communication protocol. The user is required to provide the mapper with the information required to control their device through the dpl configuration file. These can be changed at runtime by updating configmap.
Edge Site enables to run a standalone Kubernetes cluster at the edge along with KubeEdge to get full control and improve the offline scheduling capability. A Kubernetes cluster is deployed at edge location including the management control plane. For the management control plane to manage a reasonable scale of edge worker nodes, the host master node needs to have sufficient resources.
Reliable message delivery is missing between cloud and edge.
Installer currently doesn't support installation of containerd, cni-plugins.
Port mapping is not supported in CRI