The population of KubeEdge brings in community interests in the scalability and scale of KubeEdge. Now, Kubernetes clusters powered by KubeEdge, as fully tested, can stably support 100,000 concurrent edge nodes and manage more than one million pods. This report introduces the metrics used in the test, the test procedure, and the method to connect to an ocean of edge nodes.
As the first cloud-native edge computing community, KubeEdge provides solutions for cloud-edge synergy and has been widely adopted in industries including Transportation, Energy, Internet, CDN, Manufacturing, Smart campus, etc. With the accelerated deployment of KubeEdge in this area based on cloud-edge synergy, the community will improve the security of KubeEdge continuously in cloud-native edge computing scenarios.
The KubeEdge community attaches great importance to security and has set up Sig Security and Security Team to design KubeEdge system security and quickly respond to and handle security vulnerabilities. To conduct a more comprehensive security assessment of the KubeEdge project, the KubeEdge community cooperates with Ada Logics Ltd. and The Open Source Technology Improvement Fund performed a holistic security audit of KubeEdge and output a security auditing report, including the security threat model and security issues related to the KubeEdge project. Thank you to experts Adam Korczynski and David Korczynski of Ada Logics for their professional and comprehensive evaluation of the KubeEdge project, which has important guiding significance for the security protection of the KubeEdge project. Thank you Amir Montazery and Derek Zimmer of OSTIF and Cloud Native Computing Foundation (CNCF) who helped with this engagement.
The discovered security issues have been fixed and patched to the latest three minor release versions (v1.11.1, v1.10.2, v1.9.4) by KubeEdge maintainers according to the kubeedge security policy. Security advisories have been published here.
For more details of the threat model and the mitigations, Please check KubeEdge Threat Model And Security Protection Analysis: https://github.com/kubeedge/community/tree/master/sig-security/sig-security-audit/KubeEdge-threat-model-and-security-protection-analysis.md.
On Jun 21, 2022 KubeEdge released v1.11, introducing several exciting new features and enhancements that significantly improve node group management, mapper development, installation experience, and overall stability.
init and joinUsers can now 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 versions of app instances in different node groups
Limit service endpoints in the same location as the client
Two new APIs have been introduced to implement Node Group Management:
Refer to the links for more details (#3574, #3719).
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., as well as 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 link for more details (#70).
Some new sub-commands in Keadm have moved to GA, including containerized deployment, offline installation, etc. The original init and join behaviors have been replaced by the 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 are packed as container images to edge nodes for node setup.
init: CloudCore Helm Chart is integrated into init, which can be used to deploy containerized CloudCore.
join: Installing edgecore as a system service from a Docker image, no need to download from the 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 cloud-side components.
Refer to the link for more details (#3900).
init and joinThe original init and join sub-commands have been deprecated as they had issues with offline installation, etc.
Refer to the link for more details (#3900).
The new version of the lightweight engine Edged, optimized from Kubelet and integrated into edgecore, has moved to Beta. The new Edged will still communicate with the cloud through the reliable transmission tunnel.
Refer to the link for more details (Dev-Branch for beta: feature-new-edged).
If you want to use Keadm to deploy KubeEdge v1.11.0, please note that the behaviors of the init and join sub-commands have been changed.
Add custom image repo for keadm join beta (#3654)
Keadm: beta join support remote runtime (#3655)
Use sync mode to update pod status (#3658)
Make log level configurable for local up kubeedge (#3664)
Use dependency to pull images (#3671)
Move apis and client under kubeedge/cloud/pkg/ to kubeedge/pkg/ (#3683)
Add subresource field in application for API with subresource (#3693)
Add Keadm beta e2e (#3699)
Keadm beta config images: support remote runtime (#3700)
Use unified image management (#3720)
Use armhf as default for armv7/v6 (#3723)
Add ErrStatus in api-server application (#3742)
Support compile binaries with kubeedge/build-tools image (#3756)
Add min TLS version for stream server (#3764)
Adding security policy (#3778)
Chart: add cert domain config in helm chart (#3802)
Add domain support for certgen.sh (#3808)
Remove default KubeConfig for cloudcore (#3836)
Helm: Allow annotation of the cloudcore service (#3856)
Add rate limiter for edgehub (#3862)
Sync pod status immediately when status update (#3891)
On Mar 7, 2022, KubeEdge released v1.10. The new version introduces several enhancements, significantly improving the installation experience, performance testing, network communication, and Kubernetes version compatibility.
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)
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 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 link for more details. (#3637)
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 link for more details. (#281)
Some users' services use the udp protocol, and now edgemesh can also support the proxy of udp applications.
Refer to the link for more details. (#295)
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)
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 link for more details. (#3624)
If you want to deploy the KubeEdge v1.10.0, please note that the Kubernetes dependency is 1.22.6.
Remove dependency on os/exec and curl in favor of net/http (#3409, @mjlshen)
Optimize script when create stream cert (#3412, @gujun4990)
Modify the log view command after edgecore is running (#3456, @zc2638)
Optimize the iptables manager (#3461, @zhu733756)
Change the resourceType of msg issued by synccontroller (#3496, @Rachel-Shao)
Add a basic image for building various components of KubeEdge (#3513, @zc2638)
Supporting crossbuild all components (#3515, [@fisher
KubeEdge is an open source system extending native containerized application orchestration and device management to hosts at the Edge. It is built upon Kubernetes and provides core infrastructure support for networking, application deployment and metadata synchronization between cloud and edge. It also supports MQTT and allows developers to author custom logic and enable resource constrained device communication at the Edge.