github.com/jingruilea/kubeedge@v1.2.0-beta.0.0.20200410162146-4bb8902b3879/CHANGELOG.md (about) 1 2 * [v0.3.0](#v030) 3 * [Downloads for v0.3.0](#downloads-for-v030) 4 * [KubeEdge Binaries](#kubeedge-binaries) 5 * [Installer Binaries](#installer-binaries) 6 * [KubeEdge v0.3 Release Notes](#kubeedge-v03-release-notes) 7 * [0.3 What's New](#03-whats-new) 8 * [Known Issues](#known-issues) 9 * [Other Notable Changes](#other-notable-changes) 10 * [v0.3.0-beta.0](#v030-beta0) 11 * [Downloads for v0.3.0-beta.0](#downloads-for-v030-beta0) 12 * [KubeEdge Binaries](#kubeedge-binaries-1) 13 * [Installer Binaries](#installer-binaries-1) 14 * [Changelog since v0.2.1](#changelog-since-v021) 15 * [Features Added](#features-added) 16 * [Known Issues](#known-issues-1) 17 * [Other notable changes](#other-notable-changes-1) 18 * [v0.2.1](#v021) 19 * [Downloads for v0.2.1](#downloads-for-v021) 20 * [Changelog since v0.2.0](#changelog-since-v020) 21 * [Bug fixes](#bug-fixes) 22 * [Known issues](#known-issues-2) 23 * [v0.2](#v02) 24 * [Downloads for v0.2](#downloads-for-v02) 25 * [KubeEdge v0.2 Release Notes](#kubeedge-v02-release-notes) 26 * [Features added](#features-added-1) 27 * [Known issues](#known-issues-3) 28 * [Features Work In Progress (Future release)](#features-work-in-progress-future-release) 29 * [v0.1](#v01) 30 * [Downloads for v0.1](#downloads-for-v01) 31 * [KubeEdge v0.1 Release Notes](#kubeedge-v01-release-notes) 32 * [Features supported](#features-supported) 33 * [Known issues](#known-issues-4) 34 * [Features Work In Progress (Future release)](#features-work-in-progress-future-release-1) 35 36 # v0.3.0 37 38 ## Downloads for v0.3.0 39 40 ### KubeEdge Binaries 41 | filename | Size | sha512 hash | 42 | -------- | ---- | ----------- | 43 | [kubeedge-v0.3.0-linux-amd64.tar.gz](https://github.com/kubeedge/kubeedge/releases/download/v0.3.0/kubeedge-v0.3.0-linux-amd64.tar.gz) | 37.9 MB | `25761cbb6aeab1b778990acb6cd82dda0febcb8354b75636266dc39ecd9377da0e78f477220e3f2d578f51d63de678665fa1aff62c68523ae74c2496f52c17e2` | 44 | [kubeedge-v0.3.0-linux-arm.tar.gz](https://github.com/kubeedge/kubeedge/releases/download/v0.3.0/kubeedge-v0.3.0-linux-arm.tar.gz) | 34.8 MB | `fc17e3f2b01d9c54e00f5cbfb32c48d53b7ec0ef8f4a0ab8484fd164587d7d083d463ef0e4be06ab4f6e9205dc95df277c06a9e6b082450f2ffd1cb63c176d56` | 45 46 ### Installer Binaries 47 | filename | Size | sha512 hash | 48 | -------- | ---- | ----------- | 49 | [keadm-v0.3.0-linux-amd64.tar.gz](https://github.com/kubeedge/kubeedge/releases/download/v0.3.0/keadm-v0.3.0-linux-amd64.tar.gz) | 2.23 MB | `bce839fef66e0e370876dbbdc671129f3e209d03e7530992ea84bb0bc804fd0a88182db06852266a3cde80e52c0b8ae7bc8f58ff2022acb88f67dd8d6f5b11d3` | 50 51 52 # KubeEdge v0.3 Release Notes 53 54 ## 0.3 What's New 55 56 **Device Management using CRD** 57 58 This feature mainly provides APIs for managing devices from cloud and synchronize the device updates between cloud and edge. 59 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. 60 61 **Bluetooth Mapper** 62 63 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. 64 65 **Performance Test Framework** 66 67 Benchmarking framework to measure the performance against the following Service Level Objectives: 68 - Latency: time cost from the moment when the server gets the request to last byte of response sent to the users. 69 - Throughput: measure how many requests can be served within given time. 70 - Scalability: potential scaling capacity (including number of nodes, pods, devices etc. at the edge) under different load conditions. 71 - CPU Usage: measure the cpu usage of KubeEdge under different load conditions. 72 - Memory Usage: measure the memory usage of KubeEdge under different load conditions. 73 74 **KubeEdge Installer** 75 Support for basic commands to bootstrap and teardown both KubeEdge cloud and edge components. 76 Supported Commands : 77 - `kubeedge init` : bootstrap cloud prerequisites and cloud components if not already present. 78 - `kubeedge join` : add edge node in cloud api-server, bootstrap edge prerequisites and edge components if not already present. 79 - `kubeedge reset` : tears down the installed components/prerequisites. The reset action has to be done on the cloud and edge nodes separately to ensure proper cleanup. 80 81 ## Known Issues 82 83 84 - API Validation for device CRD is missing. 85 86 - UT/e2e coverage should be improved for cloud part. 87 88 - Partitioning of device configmap. 89 90 - Running edged and k8s master on same VM kills k8s master pods. 91 92 ## Other Notable Changes 93 94 - Handled the case of invalid action in scheduler module ([#563](https://github.com/kubeedge/kubeedge/pull/563), [@sujithsimon22](https://github.com/sujithsimon22)) 95 96 - Added nil pointer handling in watcher,go ([#561](https://github.com/kubeedge/kubeedge/pull/561), [@sujithsimon22](https://github.com/sujithsimon22)) 97 98 - Corrected the topic name being used in bluetooth_mapper ([#559](https://github.com/kubeedge/kubeedge/pull/559), [@sujithsimon22](https://github.com/sujithsimon22)) 99 100 - Mismatch in access mode names ([#558](https://github.com/kubeedge/kubeedge/pull/558), [@sujithsimon22](https://github.com/sujithsimon22)) 101 102 - Fix edge_core crashs when SecurityContext.Privileged pointer ([#555](https://github.com/kubeedge/kubeedge/pull/555), [@shouhong](https://github.com/shouhong)) 103 104 - Supports automatic deletion of edge containers if their pods ([#537](https://github.com/kubeedge/kubeedge/pull/537), [@shouhong](https://github.com/shouhong)) 105 106 - fix nil pointer panic possibility in deviceController ([#501](https://github.com/kubeedge/kubeedge/pull/501), [@sids-b](https://github.com/sids-b)) 107 108 - Make file changes to fix #issue 496 ([#497](https://github.com/kubeedge/kubeedge/pull/497), [@srivatsav123](https://github.com/srivatsav123)) 109 110 - Fixed restart issue of mapper ([#492](https://github.com/kubeedge/kubeedge/pull/492), [@sujithsimon22](https://github.com/sujithsimon22)) 111 112 - fix EdgeController config keys ([#490](https://github.com/kubeedge/kubeedge/pull/490), [@sids-b](https://github.com/sids-b)) 113 114 - Added README.MD for Kubeedge installer #issue-477. ([#489](https://github.com/kubeedge/kubeedge/pull/489), [@srivatsav123](https://github.com/srivatsav123)) 115 116 - fix the broken link ([#481](https://github.com/kubeedge/kubeedge/pull/481), [@lou-lan](https://github.com/lou-lan)) 117 118 - Device CRD: remove configmap when no device is bound with ([#479](https://github.com/kubeedge/kubeedge/pull/479), [@chendave](https://github.com/chendave)) 119 120 - Changed exit status from 0 to 1 when bluetooth mapper exits ([#475](https://github.com/kubeedge/kubeedge/pull/475), [@sujithsimon22](https://github.com/sujithsimon22)) 121 122 - Added Device CRD sample for CC2650 Bluetooth device ([#472](https://github.com/kubeedge/kubeedge/pull/472), [@sujithsimon22](https://github.com/sujithsimon22)) 123 124 - update setup steps in docs.kubeedge.io ([#470](https://github.com/kubeedge/kubeedge/pull/470), [@edisonxiang](https://github.com/edisonxiang)) 125 126 - Distinguish debugging information between controller and ([#462](https://github.com/kubeedge/kubeedge/pull/462), [@kadisi](https://github.com/kadisi)) 127 128 - delete useless field messageLayer ([#459](https://github.com/kubeedge/kubeedge/pull/459), [@kadisi](https://github.com/kadisi)) 129 130 - Added lableselectors logic to deploy kubeedge edgenode pod to ([#453](https://github.com/kubeedge/kubeedge/pull/453), [@pavan187](https://github.com/pavan187)) 131 132 - Fix #463: Update kubeedge architecture ([#504](https://github.com/kubeedge/kubeedge/pull/504), [@rohitsardesai83](https://github.com/rohitsardesai83)) 133 134 - docs: [ Fix #436 ] : Apply device CRDs before running cloud. ([#450](https://github.com/kubeedge/kubeedge/pull/450), [@rohitsardesai83](https://github.com/rohitsardesai83)) 135 136 137 # v0.3.0-beta.0 138 139 [Documentation](https://docs.kubeedge.io) 140 141 ## Downloads for v0.3.0-beta.0 142 143 ### KubeEdge Binaries 144 | filename | Size | sha512 hash | 145 | -------- | ---- | ----------- | 146 | [kubeedge-v0.3.0-beta.0-linux-amd64.tar.gz](https://github.com/kubeedge/kubeedge/releases/download/v0.3.0-beta.0/kubeedge-v0.3.0-beta.0-linux-amd64.tar.gz) | 34.3 MB | `7ec485e03611261b544196c83caa5136d6a364fbf01b28009215566ef0b31d60de02e439cd55e1c9a01db8e6a0c06717b17e6ec8f15704031eab890c0dd75e1a` | 147 | [kubeedge-v0.3.0-beta.0-linux-arm.tar.gz](https://github.com/kubeedge/kubeedge/releases/download/v0.3.0-beta.0/kubeedge-v0.3.0-beta.0-linux-arm.tar.gz) | 31.4 MB | `d70a016673c4ee6f1cf8dc76e0af8c54266a5e355d560093846f56ead684035af83241a1035db59486a716b15ebc40ae0188d42608cbf95a86de8b838a8e1195` | 148 149 150 ### Installer Binaries 151 | filename | Size | sha512 hash | 152 | -------- | ---- | ----------- | 153 | [keadm-v0.3.0-beta.0-linux-amd64.tar.gz](https://github.com/kubeedge/kubeedge/releases/download/v0.3.0-beta.0/keadm-v0.3.0-beta.0-linux-amd64.tar.gz) | 2.05 MB | `5775c5c1b25a9148fd592cf61e0cd671ca8fb345c63c897709bda2c479bb3a315c9f979e934fbd5a79dfcb633f793ffe948979773e65f95c65791b4ac08c3d0f` | 154 155 ## Changelog since v0.2.1 156 157 ### Features Added 158 159 160 - Device Management using CRDs : This feature mainly provides APIs 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. 161 162 163 - 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. 164 165 166 - Performance Test Framework : Benchmarking framework to measure the performance against the following Service Level Objectives: 167 - Latency: time cost from the moment when the server gets the request to last byte of response sent to the users. 168 - Throughput: measure how many requests can be served within given time. 169 - Scalability: potential scaling capacity (including number of nodes, pods, devices etc. at the edge) under different load conditions. 170 - CPU Usage: measure the cpu usage of KubeEdge under different load conditions. 171 - Memory Usage: measure the memory usage of KubeEdge under different load conditions. 172 173 174 - KubeEdge Installer : Support for basic commands to bootstrap and teardown both KubeEdge cloud and edge components. 175 Supported Commands : 176 - `kubeedge init` : bootstrap cloud prerequisites and cloud components if not already present. 177 - `kubeedge join` : add edge node in cloud api-server, bootstrap edge prerequisites and edge components if not already present. 178 - `kubeedge reset` : tears down the installed components/prerequisites. The reset action has to be done on the cloud and edge nodes separately to ensure proper cleanup. 179 180 ### Known Issues 181 182 183 - API Validation for device CRD is missing. 184 185 - UT/e2e coverage should be improved for cloud part. 186 187 - Partitioning of device configmap. 188 189 - Running edged and k8s master on same VM kills k8s master pods. 190 191 ### Other notable changes 192 193 194 - UT for devicetwin/dtmanager/twin.go. ([#300](https://github.com/kubeedge/kubeedge/pull/300), [@omung-g](https://github.com/omung-g)) 195 196 - Add Kubernetes deployment for Edge. ([#367](https://github.com/kubeedge/kubeedge/pull/367), [@edisonxiang](https://github.com/edisonxiang)) 197 198 - Adding UT for cloudhub/common/model/types.go. ([#395](https://github.com/kubeedge/kubeedge/pull/395), [@omung-g](https://github.com/omung-g)) 199 200 - output time duration per test case. ([#397](https://github.com/kubeedge/kubeedge/pull/397), [@edisonxiang](https://github.com/edisonxiang)) 201 202 - Adding unit tests for device.go. ([#376](https://github.com/kubeedge/kubeedge/pull/376), [@lidiyag](https://github.com/lidiyag)) 203 204 - Fix the nil pointer exception for missing config string ([#432](https://github.com/kubeedge/kubeedge/pull/432), [@trilokgm](https://github.com/trilokgm)) 205 206 # v0.2.1 207 ## Downloads for v0.2.1 208 | filename | Size | 209 | -------- | ---- | 210 | [kubeedge-v0.2.1-linux-amd64.tar.gz](https://github.com/kubeedge/kubeedge/releases/download/v0.2.1/kubeedge-v0.2.1-linux-amd64.tar.gz) | 34.2 MB | 211 | [kubeedge-v0.2.1-linux-arm.tar.gz](https://github.com/kubeedge/kubeedge/releases/download/v0.2.1/kubeedge-v0.2.1-linux-arm.tar.gz) | 31.4 MB | 212 213 214 215 ## Changelog since v0.2.0 216 217 ### Bug fixes 218 219 https://github.com/kubeedge/kubeedge/pull/354 220 https://github.com/kubeedge/kubeedge/pull/328 221 222 ### Known issues 223 1. service bus at edge cannot be used until router support is added in the cloud. 224 225 # v0.2 226 227 ## Downloads for v0.2 228 | filename | Size | 229 | -------- | ---- | 230 | [kubeedge-v0.2-linux-amd64.tar.gz](https://github.com/kubeedge/kubeedge/releases/download/v0.2/kubeedge-v0.2-linux-amd64.tar.gz) | 25.7 MB | 231 | [kubeedge-v0.2-linux-arm.tar.gz](https://github.com/kubeedge/kubeedge/releases/download/v0.2/kubeedge-v0.2-linux-arm.tar.gz) | 31.4 MB | 232 233 # KubeEdge v0.2 Release Notes 234 This is the second release of KubeEdge. **Cloud is there finally!** 235 236 ## Features added 237 1. Edge-controller which connects to Kubernetes api-server and sync node/pod status between edge and kubernetes api-server. 238 2. Cloudhub which is a websocket server in cloud part of kubeedge. 239 3. Internal MQTT mode in which MQTT broker is started with edge_core and removes dependency on external MQTT broker. 240 4. Integration test framework for edge. Improved edge_core unit-test coverage. 241 242 ## Known issues 243 1. We do not have any e2e tests yet. 244 2. Unit tests coverage should be improved for cloud part. 245 246 ## Features Work In Progress (Future release) 247 1. Describe device API via CRD. 248 2. Edge to Edge Communication. 249 3. Different Protocol support for KubeEdge like BLE, Zigbee,etc. 250 251 # v0.1 252 ## Downloads for v0.1 253 | filename | Size | 254 | -------- | ---- | 255 | [kubeedge-v0.1-linux-amd64.tar.gz](https://github.com/kubeedge/kubeedge/releases/download/v0.1/kubeedge-v0.1-linux-amd64.tar.gz) | 21.9 MB | 256 257 # KubeEdge v0.1 Release Notes 258 This is kubeedge's first release. 259 260 ## Features supported 261 1. A lightweight application engine running on edge node for managing user's application and monitoring node health. 262 2. Supports Kubernetes API primitives, e.g. Node, Pod, Configmap, Secrets etc. 263 3. Device twin and MQTT protocol for IoT devices talking to Edge node 264 4. Local self-governance via HTTP restful interfaces. 265 5. Integrated with Huawei Cloud IEF service for node, device and application status updates. 266 6. Edge node autonomy when its getting offline and recover post reconnection to Cloud. 267 268 ## Known issues 269 1. We do not have any e2e tests yet. 270 2. Unit tests coverage should be improved. 271 272 ## Features Work In Progress (Future release) 273 1. Develop and open-source the cloud part components. 274 2. Describe device API via CRD.