English | 简体中文
KubeEdge is built upon Kubernetes and extends native containerized application orchestration and device management to hosts at the Edge. It consists of cloud part and edge part, provides core infrastructure support for networking, application deployment and metadata synchronization between cloud and edge. It also supports MQTT which enables edge devices to access through edge nodes.
With KubeEdge it is easy to get and deploy existing complicated machine learning, image recognition, event processing and other high level applications to the Edge. With business logic running at the Edge, much larger volumes of data can be secured & processed locally where the data is produced. With data processed at the Edge, the responsiveness is increased dramatically and data privacy is protected.
KubeEdge is an incubation-level hosted project by the Cloud Native Computing Foundation (CNCF). KubeEdge incubation announcement by CNCF.
The versions before 1.8 have not been supported, please try upgrade.
- Kubernetes-native support: Managing edge applications and edge devices in the cloud with fully compatible Kubernetes APIs.
- Cloud-Edge Reliable Collaboration: Ensure reliable messages delivery without loss over unstable cloud-edge network.
- Edge Autonomy: Ensure edge nodes run autonomously and the applications in edge run normally, when the cloud-edge network is unstable or edge is offline and restarted.
- Edge Devices Management: Managing edge devices through Kubernetes native APIs implemented by CRD.
- Extremely Lightweight Edge Agent: Extremely lightweight Edge Agent(EdgeCore) to run on resource constrained edge.
How It Works
KubeEdge consists of cloud part and edge part.
In the Cloud
- CloudHub: a web socket server responsible for watching changes at the cloud side, caching and sending messages to EdgeHub.
- EdgeController: an extended kubernetes controller which manages edge nodes and pods metadata so that the data can be targeted to a specific edge node.
- DeviceController: an extended kubernetes controller which manages devices so that the device metadata/status data can be synced between edge and cloud.
On the Edge
- EdgeHub: a web socket client responsible for interacting with Cloud Service for the edge computing (like Edge Controller as in the KubeEdge Architecture). This includes syncing cloud-side resource updates to the edge, and reporting edge-side host and device status changes to the cloud.
- Edged: an agent that runs on edge nodes and manages containerized applications.
- EventBus: a MQTT client to interact with MQTT servers (mosquitto), offering publish and subscribe capabilities to other components.
- ServiceBus: an HTTP client to interact with HTTP servers (REST), offering HTTP client capabilities to components of cloud to reach HTTP servers running at edge.
- DeviceTwin: responsible for storing device status and syncing device status to the cloud. It also provides query interfaces for applications.
- MetaManager: the message processor between edged and edgehub. It is also responsible for storing/retrieving metadata to/from a lightweight database (SQLite).
|Kubernetes 1.17||Kubernetes 1.18||Kubernetes 1.19||Kubernetes 1.20||Kubernetes 1.21||Kubernetes 1.22||Kubernetes 1.23|
|KubeEdge HEAD (master)||✓||✓||✓||✓||✓||✓||✓|
✓KubeEdge and the Kubernetes version are exactly compatible.
+KubeEdge has features or API objects that may not be present in the Kubernetes version.
-The Kubernetes version has features or API objects that KubeEdge can't use.
Get start with this doc.
See our documentation on kubeedge.io for more details.
To learn deeply about KubeEdge, try some examples on examples.
Regular Community Meeting:
- Europe Time: Wednesdays at 16:30-17:30 Beijing Time (biweekly, starting from Feb. 19th 2020). (Convert to your timezone.)
- Pacific Time: Wednesdays at 10:00-11:00 Beijing Time (biweekly, starting from Feb. 26th 2020). (Convert to your timezone.)
If you need support, start with the troubleshooting guide, and work your way through the process that we've outlined.
If you have questions, feel free to reach out to us in the following ways:
If you're interested in being a contributor and want to get involved in developing the KubeEdge code, please see CONTRIBUTING for details on submitting patches and the contribution workflow.
A third party security audit of KubeEdge has been completed in July 2022. Additionally, the KubeEdge community completed an overall system security analysis of KubeEdge. The detailed reports are as follows.
Reporting security vulnerabilities
We encourage security researchers, industry organizations and users to proactively report suspected vulnerabilities to our security team (
email@example.com), the team will help diagnose the severity of the issue and determine how to address the issue as soon as possible.
For further details please see Security Policy for our security process and how to report vulnerabilities.
KubeEdge is under the Apache 2.0 license. See the LICENSE file for details.