Project: KubeEdge (Provisioning / Automation & Configuration)
File: CHANGELOG-1.13.md

* * * * * * * * * * * * * Download v1.13.5 in the . Fix featuregates didn't take effect in edged. (, ) Supports installing edgecore without installing the CNI plugin. (, ) Download v1.13.4 in the . Resolve the deployment order dependency between mapper and device. (, ) Fix copy resources from the image throws nil runtimg error. (, ) Fix error logs when nodes repeatedly join different node groups. (, , ) Bump Kubernetes to the newest patch version 1.23.17. (, ) Fix serviceaccount token not being deleted in edge DB. (, ) Download v1.13.3 in the . Fix upgrade time layout and lost time value issue. (, ) Fix start edgecore failed when using systemd cgroupdriver. (, ) Fix remove pod cache failed. (, ) Fix Keadm process stops abnormally when Keadm upgrade stops edgecore process. (, ) Download v1.13.2 in the . Fixed the kubeedge-version flag does not take effect in init and manifest generate command. (, ) Fix throws nil runtime error when decode AdmissionReview failed. (, ) Fix repeatedly reporting history device message to cloud. (, ) Download v1.13.1 in the . Fix MQTT container exited abnormally when edgecore using cri runtime. (, ) Deal with error in delete pod upstream msg. (, ) Update pod db when patch pod successfully. (, ) Use nodeIP initialization in Kubelet, support reporting nodeIP dynamically . (, ) Fix delete statefulset pod failed. (, ) Fix container terminated when edgecore restart. (, ) Fix iptables-manager and controller-manager image name. (, ) Wait for cache sync when cloudcore reboot. (, ) 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`. Download v1.13.0 in the . CloudCore memory usage is reduced by 40%, through unified generic Informer and reduce unnecessary cache. () () List-watch dynamicController processing optimization, each watcher has a separate channel and goroutine processing to improve processing efficiency () Added list-watch synchronization mechanism between cloud and edge and add dynamicController watch gc mechanism () Removed 10s hard delay when offline nodes turn online () Added prometheus monitor server and a metric connected_nodes to

This metric tallies the number of connected nodes each cloudhub instance () Added pprof for visualization and analysis of profiling data () CloudCore configuration is now automatically adjusted according to nodeLimit to adapt to the number of nodes of different scales () KubeEdge is proud to announce that we are digitally signing all release artifacts (including binary artifacts and container images). Signing artifacts provides end users a chance to verify the integrity of the downloaded resource. It allows to mitigate man-in-the-middle attacks directly on the client side and therefore ensures the trustfulness of the remote serving the artifacts. By doing this, we reached the SLSA security assessment level L3 () Remove the token field in the edge node configuration file edgecore.yaml to eliminate the risk of edge information leakage () Upgrade the vendered kubernetes version to v1.23.15, users are now able to use the feature of new version on the cloud and on the edge side. Refer to the link for more details. () Modbus Device Mapper based on DMI is provided, which is used to access Modbus protocol devices and uses DMI to synchronize the management plane messages of devices with edgecore. Refer to the link for more details. () Users now able to trigger rolling upgrade for edge nodes from cloud, and specify number of concurrent upgrade nodes with `nodeupgradejob.spec.concurrency`. The default Concurrency value is 1, which means upgrade edge nodes one by one. Refer to the link for more details. () KubeEdge has provided the runner of the conformance test, which contains the scripts and related files of the conformance test. Refer to the link for more details. () The tunnel stream of the edge-tunnel module is used to manage the data stream state of the tunnel. Users can obtain a stable and configurable tunnel stream to ensure the reliability of user application traffic forwarding. Users can configure the cache size of tunnel stream according to `TunnelLimitConfig` to support larger application relay traffic. Refer to the link for more details. () Cancel the restrictions on the relay to ensure the stability of the user's streaming application or long link application. Refer to the link for more details. () EdgeCore now uses `containerd` runtime by default on KubeEdge v1.13. If you want to use `docker` runtime, you must set `edged.containerRuntime=docker` and corresponding docker configuration like `DockerEndpoint`, `RemoteRuntimeEndpoint` and `RemoteImageEndpoint` in EdgeCore.