See CHANGELOG-1.16.md for details.

See CHANGELOG-1.13.md for details.

See CHANGELOG-1.12.md for details.

See CHANGELOG-1.9.md for details.

See CHANGELOG-1.10.md for details.

See CHANGELOG-1.11.md for details.

See CHANGELOG-1.7.md for details.

See CHANGELOG-1.4.md for details.

Notable Changes

• Keadm: support raspbian (https://github.com/kubeedge/kubeedge/pull/1779, @daixiang0)
• Implement device management enhance (https://github.com/kubeedge/kubeedge/pull/1790, @luogangyi)
• Support edge certificate rotation (https://github.com/kubeedge/kubeedge/pull/1838, @XJangel)
• Add tree to store copy of dependency's license (https://github.com/kubeedge/kubeedge/pull/1847, @kevin-wangzefeng)
• add garbage collection of reliablesyncs when node unregisters (https://github.com/kubeedge/kubeedge/pull/1855, @ls889)
• fix too long time to get node ready when reconnect (https://github.com/kubeedge/kubeedge/pull/1670, @fisherxu)
• fix cpu limit does not take effect issue (https://github.com/kubeedge/kubeedge/pull/1866, @Baoqiang-Zhang)
• Auto detect sandbox image (https://github.com/kubeedge/kubeedge/pull/1874, @daixiang0 )
• Run edgecore as system service (https://github.com/kubeedge/kubeedge/pull/1962, @dingyin)
• Update vendor to Kubernetes 1.18 (https://github.com/kubeedge/kubeedge/pull/1982, @dingyin)
• extend property types (https://github.com/kubeedge/kubeedge/pull/2014, @luogangyi)

Bug fixs

• fix wrong use of e.namespace when get imagePullSecret (https://github.com/kubeedge/kubeedge/pull/1765, @GsssC)
• fix wrong parse operation when service url is short (https://github.com/kubeedge/kubeedge/pull/1775, @XiaoJiangWang)
• delay the volume mount until the pods are retrieved from metaManger and added to managers when edgecore starts (https://github.com/kubeedge/kubeedge/pull/1809, @GsssC)
• edged.go: Fix pod sync copied from kubelet (https://github.com/kubeedge/kubeedge/pull/1819, @faicker)
• Improve metrics connection (https://github.com/kubeedge/kubeedge/pull/1887, @Poor12)
• fix use certificate from local directory problem (https://github.com/kubeedge/kubeedge/pull/1925, @threestoneliu)
• Process of bluetooth mapper scheduler seems wrong (https://github.com/kubeedge/kubeedge/pull/1940, @sailorvii)
• Fix device configMap can not be re-created (https://github.com/kubeedge/kubeedge/pull/1949, @daixiang0)
• fixed goroutine leak, when ws connection reconnect, but fifo's channel no close (https://github.com/kubeedge/kubeedge/pull/2019, @loongify)

See CHANGELOG-1.3.md for details.

See CHANGELOG-1.3.md for details.

Notable Changes

• Add edge-node certs bootstrap (https://github.com/kubeedge/kubeedge/pull/1605, @fisherxu, @ls889, @XJangel)
• support kubectl logs to fetch logs of pods at edge (https://github.com/kubeedge/kubeedge/pull/1606, @kadisi)
• CloudCore now supports HA with active-standby mode (https://github.com/kubeedge/kubeedge/pull/1600, @GsssC, @kevin-wangzefeng)
• Add feature to provision VM workload (https://github.com/kubeedge/kubeedge/pull/1618, @dingyin)
• A set of component config API fiels have been updated with capitalization (https://github.com/kubeedge/kubeedge/pull/1616, @kevin-wangzefeng)
• Add support for CRI-O as light-weight runtime (https://github.com/kubeedge/kubeedge/pull/1610, @chendave)
• Edge nodes are now registered with kubernetes.io/arch kubernetes.io/os labels automatically (https://github.com/kubeedge/kubeedge/pull/1601, @kevin-wangzefeng)
• Add metrics interfaces at edge (https://github.com/kubeedge/kubeedge/pull/1573, @fisherxu)
• keadm now support installing KubeEdge on CentOS (https://github.com/kubeedge/kubeedge/pull/1536, @FengyunPan2)
• edgecore: support configmap environment variable (https://github.com/kubeedge/kubeedge/pull/1518, @xmwilldo)
• EdgeMesh now doesn't rely on initContainers for intialization (https://github.com/kubeedge/kubeedge/pull/1380, liuzhiyi1993)

Bug fixes

• fix GroupName for devices apis register (https://github.com/kubeedge/kubeedge/pull/1594, @bretagne-peiqi)
• fix message handleserver close channel panic (https://github.com/kubeedge/kubeedge/pull/1557, @drcwr)
• Fix panic in cloudcore (https://github.com/kubeedge/kubeedge/pull/1552, @fisherxu)

See CHANGELOG-1.2.md for details.

See CHANGELOG-1.1.md for details.

Notable changes

• Fix edge_core cannot connect to edgecontroller after disconnecting once (#870, @shouhong)

• Raspberry Pi3/4 cross build (#903, @subpathdev)

• Upgrade to Kubernetes v1.15 (#941, @edisonxiang)

• Add New Feature: support dockershim in edged. (#829, @arcanique)

• Use go mod (#947, @subpathdev)

• Rename device dir to mappers which places mappers (#966, @fisherxu)

• New feature: L4 Proxy support in edgemesh (#970, @arcanique)

• Initialize feature lifecycle doc (#850, @kevin-wangzefeng)

• Change go version from go 1.11 to go 1.12 (#982, @kadisi)

• Add admission webhook for validate device CRD (#984, @chendave)

• Rename edgecontroller to cloudcore (#988, @fisherxu)

• Rename edge_core to edgecore (#999, @kexun)

• Unifying logging library to klog (#1019, @kadisi)

• Add in-tree csi plugin implementations (#1047, @edisonxiang)

• Add csi driver from kubeedge (#1059, @edisonxiang)

• Add local up kubeedge script (#1085, @fisherxu)

v1.0 What's New

Edge Mesh

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.

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.

Modbus Mapper

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

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.

Known Issues

• 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

Other notable changes

• Pods created using CRI on deletion remain in terminating status. (#755, @gpinaik)

• fix bug: replace value in key, value by expected (#759, @RicardoZPHuang)

• update edge_core version to reflect the vendor k8s and kubeedge version (#761, @sids-b)

• Edgesite documentation (#737, @naveensriram)

• add edgemesh end to end test guide (#758, @anyushun)

• Changes made to Installer to support CRI (#795, @srivatsav123)

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.