Features added

Edge Mesh

This feature aims to support service mesh capabilities on the edge to support microservice communication cross cloud and edge. In v1.0 release, pod-to-pod communication on the same edge node or across
edge nodes in the same subnet is possible.

CRI support

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.

Edge Site

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.

Modbus Mapper

Modbus Mapper is an application that is used to connect and control devices that use Modbus(RTU/TCP) as a communication protocol.

Changelog since v0.3.0-beta.0

Other Notable Changes

• Handled the case of invalid action in scheduler module (#563, @sujithsimon22)
• Added nil pointer handling in watcher,go (#561, @sujithsimon22)
• Corrected the topic name being used in bluetooth_mapper (#559, @sujithsimon22)
• Mismatch in access mode names (#558, @sujithsimon22)
• Fix edge_core crashs when SecurityContext.Privileged pointer (#555, @shouhong)
• Supports automatic deletion of edge containers if their pods (#537, @shouhong)
• fix nil pointer panic possibility in deviceController (#501, @sids-b)
• Make file changes to fix #issue 496 (#497, @srivatsav123)
• Fixed restart issue of mapper (#492, @sujithsimon22)
• fix EdgeController config keys (#490, @sids-b)
• Added README.MD for Kubeedge installer #issue-477. (#489, @srivatsav123)
• fix the broken link (#481, @lou-lan)
• Device CRD: remove configmap when no device is bound with (#479, @chendave)
• Changed exit status from 0 to 1 when bluetooth mapper exits (#475, @sujithsimon22)
• Added Device CRD sample for CC2650 Bluetooth device (#472, @sujithsimon22)
• update setup steps in docs.kubeedge.io (#470, @edisonxiang)
• Distinguish debugging information between controller and (#462, @kadisi)
• delete useless field messageLayer (#459, @kadisi)
• Added lableselectors logic to deploy kubeedge edgenode pod to (#453, @pavan187)
• Fix #463: Update kubeedge architecture (#504, @rohitsardesai83)
• docs: [ Fix #436 ] : Apply device CRDs before running cloud. (#450, @rohitsardesai83)

Features added

1. Device Management using CRD’s : This feature mainly provides api’s for managing devices from cloud and synchronize the device updates between cloud and edge. DeviceController is the module in cloud which is responsible for watching on devices and devicemodels and syncing the data to edge. DeviceController is also responsible for receiving the device-twin updates sent from edge and making the changes in cloud(apiserver). DeviceController also creates a configmap for each node and adds the deviceInstances, protocols, properties and propertyVisitors in it. This configmap can be consumed by any application like mapper and used to configure/control devices.

2. Bluetooth Mapper : Bluetooth Mapper is an application that is used to connect and control devices that use bluetooth as a communication protocol. It consumes the configmap generated by device-controller and reuires a configuration file for information not present in configmap. Configurations can be changed at runtime by providing the input through the MQTT broker. It can run schedule based actions and converts data received from devices into edge_core expected format.

3. Performance Test Framework : Benchmarking framework to measure the performance against the following Service Level Objectives:

• Latency: time cost from the moment when the server gets the request to last byte of response sent to the users.

• Throughput: measure how many requests can be served within given time.

• Scalability: potential scaling capacity (including number of nodes, pods, devices etc. at the edge) under different load conditions.

• CPU Usage: measure the cpu usage of KubeEdge under different load conditions.

• Memory Usage: measure the memory usage of KubeEdge under different load conditions.

4. KubeEdge Installer : Support for basic commands to bootstrap and teardown both KubeEdge cloud and edge components.
   Supported Commands :
   • kubeedge init : bootstrap cloud prerequisites and cloud components if not already present.
   • kubeedge join : add edge node in cloud api-server, bootstrap edge prerequisites and edge components if not already present.
   • kubeedge reset : for cloud node teardown cloud components and prerequites. For edge node teardown edge components and prerequisites.

Known issues

• Api Validation for device controller is missing.

• UT/e2e coverage should be improved for cloud part.

• Partitioning of device configmap.

• Running edged and k8s master on same VM kills k8s master pods.

Features Work In Progress (Future release)

• CRI support in edged.

• EdgeMesh for edge to edge communication.

• Evaluation and enhancement of cloud-edge websocket connection using QUIC.

• EdgeSite support for KubeEdge.

Bug fixes

https://github.com/kubeedge/kubeedge/pull/354
https://github.com/kubeedge/kubeedge/pull/328

Known issues

1. service bus at edge cannot be used until router support is added in the cloud.

This is the second release of KubeEdge. Cloud is there finally!

Features added

1. Edge-controller which connects to Kubernetes api-server and sync node/pod status between edge and kubernetes api-server.
2. Cloudhub which is a websocket server in cloud part of kubeedge.
3. Internal MQTT mode in which MQTT broker is started with edge_core and removes dependency on external MQTT broker.
4. Integration test framework for edge. Improved edge_core unit-test coverage.

Known issues

1. We do not have any e2e tests yet.
2. Unit tests coverage should be improved for cloud part.

Features Work In Progress (Future release)

1. Describe device API via CRD.
2. Edge to Edge Communication.
3. Different Protocol support for KubeEdge like BLE, Zigbee,etc

This is kubeedge's first release.

Features supported

1. A lightweight application engine running on edge node for managing user's application and monitoring node health.
2. Supports Kubernetes API primitives, e.g. Node, Pod, Configmap, Secrets etc.
3. Device twin and MQTT protocol for IoT devices talking to Edge node
4. Local self-government via HTTP restful interfaces.
5. Integrated with Huawei Cloud IEF service for node, device and application status updates.
6. Edge node autonomy when its getting offline and recover post reconnection to Cloud.

Known issues

1. We do not have any e2e tests yet.
2. Unit tests coverage should be improved.

Features Work In Progress (Future release)

1. Develop and open-source the cloud part components.
2. Describe device API via CRD.