Skip to content

Latest commit

 

History

History
199 lines (137 loc) · 13.1 KB

CHANGELOG-1.11.md

File metadata and controls

199 lines (137 loc) · 13.1 KB

v1.11.3

Downloads for v1.11.3

Download v1.11.3 in the v1.11.3 release page.

KubeEdge v1.11.3 Release Notes

Changelog since v1.11.2

Important Steps before Upgrading for 1.11.3

  • In previous versions, when edge node uses remote runtime (not docker runtime), using keadm join and specifying --with-mqtt=true to install edgecore will cause the Mosquitto container exits abnormally. In this release, this problem has been fixed. Users can specify --with-mqtt=true to start Mosquitto container when installing edgecore with keadm join.

v1.11.2

Downloads for v1.11.2

Download v1.11.2 in the v1.11.2 release page.

KubeEdge v1.11.2 Release Notes

Changelog since v1.11.1

  • Fix pod running on edge node has invalid serviceaccount token. (#4204, @vincentgoat)
  • Fix: Ignore the cache timestamp of the MachineInfo Metrics. (#4178, @tonyzaizai)
  • Fix residual terminating pods problem after edge node. (#4194, @vincentgoat)
  • Fix failed to rotate log for container for docker runtime. (#4217, @wackxu)
  • 1.fix delete pod terminating sometimes. 2.fix update pod status timeout. 3.fix pod condition remain ready false when node status changes from offline to online. (#4215, @wackxu)
  • Fix delete and create same name pod failed occasionally. (#4214, @wackxu)

v1.11.1

Downloads for v1.11.1

Download v1.11.1 in the v1.11.1 release page.

KubeEdge v1.11.1 Release Notes

Changelog since v1.11.0

v1.11.0

Downloads for v1.11.0

Download v1.11.0 in the v1.11.0 release page.

KubeEdge v1.11 Release Notes

1.11 What's New

Node Group Management

Users can deploy applications to several node groups without writing deployment for every group. Node group management helps users to:

  • Manage nodes in groups
  • Spread apps among node groups
  • Run different version of app instances in different node groups
  • Limit service endpoints in the same location as the client

Introduced two new APIs below to implement Node Group Management.

  • NodeGroup API: represents a group of nodes that have the same labels.
  • EdgeApplication API: contains the template of the application orgainzed by node groups, and the information of how to deploy different editions of the application to different node groups.

Refer to the links for more details. (#3574, #3719)

Mapper SDK

Mapper-sdk is a basic framework written in go. Based on this framework, developers can more easily implement a new mapper. Mapper-sdk has realized the connection to kubeedge, provides data conversion, and manages the basic properties and status of devices, etc. Basic capabilities and abstract definition of the driver interface. Developers only need to implement the customized protocol driver interface of the corresponding device to realize the function of mapper.

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

Beta sub-commands in Keadm to GA

Some new sub-commands in keadm move to GA, including containerized deployment, offline installation, etc. Original init and join behaviors are replaced by implementation from beta init and beta join:

  • CloudCore will be running in containers and managed by Kubernetes Deployment by default.

  • keadm now downloads releases that packed as container image to edge nodes for node setup.

  • init: CloudCore Helm Chart is integrated in init, which can be used to deploy containerized CloudCore.

  • join: Installing edgecore as system service from docker image, no need to download from github release.

  • reset: Reset the node, clean up the resources installed on the node by init or join. It will automatically detect the type of node to clean up.

  • manifest generate: Generate all the manifests to deploy the cloudside components.

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

Deprecation of original init and join

Original init and join are deprecated, they have problems with offline installation, etc.

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

Next-gen Edged to Beta: Suitable for more scenarios

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

Refer to the links for more details. (Dev-Branch for beta: feature-new-edged)

Important Steps before Upgrading

If you want to use keadm to deploy the KubeEdge v1.11.0, please note that the keadm init and join behaviors have been changed.

Other Notable Changes

Bug Fixes