Skip to content

Latest commit

 

History

History
211 lines (134 loc) · 12.5 KB

CHANGELOG-1.10.md

File metadata and controls

211 lines (134 loc) · 12.5 KB

v1.10.3

Downloads for v1.10.3

Download v1.10.3 in the v1.10.3 release page.

KubeEdge v1.10.3 Release Notes

Changelog since v1.10.2

  • Fix pod running on edge node has invalid serviceaccount token. (#4205, @vincentgoat)
  • Fix: Ignore the cache timestamp of the MachineInfo Metrics. (#4179, @tonyzaizai)
  • Fix residual terminating pods problem after edge node. (#4193, @vincentgoat)
  • Fix sendresp stuck occasionally when sendsync receive select. (#4211, @wackxu)
  • Fix delete and create same name pod failed occasionally. (#4223, @wackxu)

v1.10.2

Downloads for v1.10.2

Download v1.10.2 in the v1.10.2 release page.

KubeEdge v1.10.2 Release Notes

Changelog since v1.10.1

v1.10.1

Downloads for v1.10.1

Download v1.10.1 in the v1.10.1 release page.

KubeEdge v1.10.1 Release Notes

Changelog since v1.10.0

v1.10.0

Downloads for v1.10.0

Download v1.10.0 in the v1.10.0 release page.

KubeEdge v1.10 Release Notes

1.10 What's New

Installation Experience Improvement with Keadm

Keadm adds some new sub-commands to improve the user experience, including containerized deployment, offline installation, etc. New sub-commands including: beta, config.

beta provides some sub-commands that are still in testing, but have complete functions and can be used in advance. Sub-commands including: beta init, beta manifest generate, beta join, beta reset.

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

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

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

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

config is used to configure kubeedge cluster, like cluster upgrade, API conversion, image preloading. Now the image preloading has supported, sub-commands including: config images list, config images pull.

  • config images list: List all images required for kubeedge installation.

  • config images pull: Pull all images required for kubeedge installation.

Refer to the links for more details. (#3517, #3540, #3554, #3534)

Preview version for Next-gen Edged: Suitable for more scenarios

A new version of the lightweight engine Edged, which is optimized from kubelet and integrated in edgecore, and occupies less resource. Users can customize lightweight optimization according to their needs.

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

Edgemark: Support large-scale KubeEdge cluster performance testing

Edgemark is a performance testing tool inherited from Kubemark. The primary use case of Edgemark is also scalability testing, it allows users to simulate edge clusters, which can be much bigger than the real ones.

Edgemark consists of two parts: real cloud part components and a set of "Hollow" Edge Nodes. In "Hollow" Edge Nodes, EdgeCore runs in container. The edged module runs with an injected mock CRI part that doesn't do anything. So the hollow edge node doesn't actually start any containers, and also doesn't mount any volumes.

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

EdgeMesh proxy tunnel supports quic

Users can choose edgemesh's proxy tunnel as quic protocol to transmit data. In edge scenarios, nodes are often in a weak network environment. Compared with the traditional tcp protocol, the quic protocol has better performance and QoS in the weak network environment.

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

EdgeMesh supports proxy for udp applications

Some users' services use the udp protocol, and now edgemesh can also support the proxy of udp applications.

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

EdgeMesh support SSH login between cloud-edge/edge-edge nodes

Edge nodes are generally distributed in the Private network environment, but it is often necessary to ssh login and operate the edge node. EdgeMesh provide a socks5proxy based on the tunnel inside EdgeMesh, which supports forwarding ssh requests from cloud/edge nodes to edge nodes.

Refer to the links for more details. (#258, #242)

Kubernetes Dependencies Upgrade

Upgrade the vendered kubernetes version to v1.22.6, users now can use the feature of new version on the cloud and on the edge side.

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

Important Steps before Upgrading

If you want to deploy the KubeEdge v1.10.0, please note that the Kubernetes dependency is 1.22.6.

Other Notable Changes

Bug Fixes