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

* * * * * * * * * * * * * * * * * Download v1.12.7 in the . Fix featuregates didn't take effect in edged. (, ) Supports installing edgecore without installing the CNI plugin. (, ) Download v1.12.6 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.22.17. (, ) Fix serviceaccount token not being deleted in edge DB. (, ) Download v1.12.5 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. (, ) Fix mqtt container would not start when using custom registry. (, ) Download v1.12.4 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.12.3 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 . (, ) 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.12.2 in the . Fix prober not work in edgecore. (, ) Optimize convert Kubelet flags, support more Kubelet flags. (, ) Fix force delete pod when edgecore reconnect. (, ) Download v1.12.1 in the . Fix binary edgecore incomplete during keadm join using remote-runtime (, ) keadm reset supports remote runtime remove mqtt container. (, ) bugfix patch operation in quic. (, ) cluster support quic and fix failed quic e2e. (, ) fix edgeconfig nodeLabels converted to kubelet nodeLabels. (, ) bugfix logs/exec. (, ) use objectsync to construct msg object when objectsync uid not equal (, ) Download v1.12.0 in the

DMI makes KubeEdge's IoT device management more pluggable and modular in Cloud Native way, which will cover Device Lifecycle Management, Device Operation, Device Data Management. Device Lifecycle Management: Making IOT device's lifecycle management as easy as managing a pod with simplifies operations Device Operation: Providing the ability to operate devices through Kubernetes API Device Data Management: Separate from device management, the data can be consumed by local application or sync to cloud in special tunnel Refer to the links for more details. (, ) New version of the lightweight engine Edged, optimized from kubelet and integrated in edgecore, move to GA. New Edged will still communicate with the cloud through the reliable transmission tunnel. Refer to the links for more details. () Compared with the previous centralized relay mode, EdgeMesh HA mode can set up multiple relay nodes. When some relay nodes break down, other relay nodes can continue to provide relay services, which avoids single point of failure and greatly improves system stability. In addition, a relay node that is too far away will cause a high latency. The HA relay node capability can provide intermediate nodes to shorten the latency. The mDNS enables nodes in a LAN to communicate with each other without having to connect to an external network. Refer to the links for more details. Introduce NodeUpgradeJob v1alpha1 API to upgrade edge nodes from cloud now. With NodeUpgradeJob API and Controller, users can: Using NodeUpgradeJob API to upgrade selected edge nodes from cloud If upgrade fails, rollback to the original version Refer to the links for more details. (, ) Authorization for Edge Kube-API Endpoint is now available. Third-party plugins and applications that depends on Kubernetes APIs on edge nodes must use bearer token to talk to kube-apiserver via https server in MetaServer. Refer to the links for more details. (, ) GigE Device Mapper with Golang implementation is provided, which is used to access GigE Vision protocol cameras. Refer to the links for more details. () If you want to upgrade KubeEdge to v1.12, the configuration file in EdgeCore has upgraded to v1alpha2, you must modify your configuration file of edged in EdgeCore to adapt the new edged. If you want to use authorization for Edge Kube-API Endpoint, please enabled `RequireAuthorization` feature through feature gate both in CloudCore and EdgeCore. If `RequireAuthorization` feature is enabled, metaServer will only serve for https request. If you want to upgrade edgemesh to v1.12, you do not need to deploy the existing edgemesh-server, and you need to configure relayNodes. If you want to run EdgeMesh v1.12 on KubeEdge v1.12, and use https request to talk to KubeEdge, you must set `kubeAPIConfig.metaServer.security.enable=true`.