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

* * * * * * * * * * * * * Download v1.14.5 in the . Fix featuregates didn't take effect in edged. (, ) Supports installing edgecore without installing the CNI plugin. (, ) Download v1.14.4 in the . Fix the bug in local-up mode that causes cni to not launch. (, ) Resolve the deployment order dependency between mapper and device. (, ) Fix MetaServer panic with set StrictSerializer when handling create and update. (, ) Remove unnecessary pid namespace config in copy-resource. (, ) Fix error logs when nodes repeatedly join different node groups. (, , ) Bump Kubernetes to the newest patch version 1.24.17. (, ) Fix serviceaccount token not being deleted in edge DB. (, ) Download v1.14.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.14.2 in the . Fixed the cloudcore panic caused when using ClusterObjectSyncs resource. (, ) 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.14.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 parsing response message failed in metaclient. (, ) 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

Users can specify `--with-mqtt=true` to start Mosquitto container when installing edgecore with `keadm join`. Download v1.14.0 in the . The Kube-API endpoint for edge applications is implemented through MetaServer in edegcore. However, in previous versions, the authentication and authorization of Kube-API endpoint are performed in the cloud, which prevents authentication and authorization especially in offline scenarios on the edge node. In this release, the authentication and authorization functionalities are implemented within the MetaServer at edge, which allows for limiting the access permissions of edge applications when accessing Kube-API endpoint at edge. Refer to the link for more details. () The cluster scope resource can guarantee deliver to the edge side reliably since this release, especially include using list-watch global resources, the cluster scope resource can be delivered to the edge side reliably, and the edge applications can work normally. Refer to the link for more details. () Upgrade the vendered kubernetes version to v1.24.14, users are now able to use the feature of new version on the cloud and on the edge side. Note: The dockershim has been removed, which means users can't use docker runtime directly in this release. Refer to the link for more details. () KubeEdge already support `kubectl logs/exe` command, `kubectl attach` is supported in this release. `kubectl attach` command can attach to a running container at edge node. Users can execute these commands in the cloud and no need to operate on the edge nodes. Refer to the link for more details. () KubeEdge dashboard provides a graphical user interface (GUI) for managing and monitoring your KubeEdge clusters. It allows users to manage edge applications running in the cluster and troubleshoot them. Refer to the link for more details. (https://github.com/kubeedge/dashboard) On KubeEdge v1.14, EdgeCore has removed the dockeshim support, so users can only use `remote` type runtime, and uses `containerd` runtime by default. If you want to use `docker` runtime, you must first set `edged.containerRuntime=remote` and corresponding docker configuration like `RemoteRuntimeEndpoint` and `RemoteImageEndpoint` in EdgeCore, then install the cri-dockerd tools as docs below: https://github.com/kubeedge/kubeedge/issues/4843