[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-9914":3},{"id":4,"name":5,"fullName":6,"owner":5,"repo":5,"description":7,"homepage":8,"htmlUrl":9,"language":10,"languages":9,"totalLinesOfCode":9,"stars":11,"forks":12,"watchers":13,"openIssues":14,"contributorsCount":15,"subscribersCount":15,"size":15,"stars1d":16,"stars7d":17,"stars30d":18,"stars90d":15,"forks30d":15,"starsTrendScore":19,"compositeScore":20,"rankGlobal":9,"rankLanguage":9,"license":21,"archived":22,"fork":22,"defaultBranch":23,"hasWiki":24,"hasPages":22,"topics":25,"createdAt":9,"pushedAt":9,"updatedAt":37,"readmeContent":38,"aiSummary":39,"trendingCount":15,"starSnapshotCount":15,"syncStatus":16,"lastSyncTime":40,"discoverSource":41},9914,"kubeedge","kubeedge\u002Fkubeedge","Kubernetes Native Edge Computing Framework (project under CNCF)","https:\u002F\u002Fkubeedge.io",null,"Go",7472,1935,174,728,0,2,12,34,10,40.86,"Apache License 2.0",false,"master",true,[26,27,28,29,30,31,32,33,34,35,36],"cloud-native","cncf","container","device-management","docker","edge-computing","golang","iot","kubernetes","mosquitto","mqtt","2026-06-12 02:02:14","# KubeEdge\n[![Go Report Card](https:\u002F\u002Fgoreportcard.com\u002Fbadge\u002Fgithub.com\u002Fkubeedge\u002Fkubeedge)](https:\u002F\u002Fgoreportcard.com\u002Freport\u002Fgithub.com\u002Fkubeedge\u002Fkubeedge)\n[![LICENSE](https:\u002F\u002Fimg.shields.io\u002Fgithub\u002Flicense\u002Fkubeedge\u002Fkubeedge.svg?style=flat-square)](\u002FLICENSE)\n[![Releases](https:\u002F\u002Fimg.shields.io\u002Fgithub\u002Frelease\u002Fkubeedge\u002Fkubeedge\u002Fall.svg?style=flat-square)](https:\u002F\u002Fgithub.com\u002Fkubeedge\u002Fkubeedge\u002Freleases)\n[![CII Best Practices](https:\u002F\u002Fbestpractices.coreinfrastructure.org\u002Fprojects\u002F3018\u002Fbadge)](https:\u002F\u002Fbestpractices.coreinfrastructure.org\u002Fprojects\u002F3018)\n\n\u003Cimg src=\".\u002Fdocs\u002Fimages\u002Fkubeedge-logo-only.png\">\n\nEnglish | [简体中文](.\u002FREADME_zh.md)\n\nKubeEdge is built upon Kubernetes and extends native containerized application orchestration and device management to hosts at the Edge.\nIt consists of cloud part and edge part, provides core infrastructure support for networking, application deployment and metadata synchronization\nbetween cloud and edge. It also supports **MQTT** which enables edge devices to access through edge nodes.\n\nWith KubeEdge it is easy to get and deploy existing complicated machine learning, image recognition, event processing and other high level applications to the Edge.\nWith business logic running at the Edge, much larger volumes of data can be secured & processed locally where the data is produced.\nWith data processed at the Edge, the responsiveness is increased dramatically and data privacy is protected.\n\nKubeEdge is a graduation-level hosted project by the [Cloud Native Computing Foundation](https:\u002F\u002Fcncf.io) (CNCF). KubeEdge graduation [announcement](https:\u002F\u002Fwww.cncf.io\u002Fannouncements\u002F2024\u002F10\u002F15\u002Fcloud-native-computing-foundation-announces-kubeedge-graduation\u002F) by CNCF.\n\n## Advantages\n\n- **Kubernetes-native support**: Managing edge applications and edge devices in the cloud with fully compatible Kubernetes APIs.\n- **Cloud-Edge Reliable Collaboration**: Ensure reliable messages delivery without loss over unstable cloud-edge network.\n- **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.\n- **Edge Devices Management**: Managing edge devices through Kubernetes native APIs implemented by CRD.\n- **Extremely Lightweight Edge Agent**: Extremely lightweight Edge Agent(EdgeCore) to run on resource constrained edge.\n\n\n## How It Works\n\nKubeEdge consists of cloud part and edge part.\n\n### Architecture\n\n\u003Cdiv  align=\"center\">\n\u003Cimg src=\".\u002Fdocs\u002Fimages\u002Fkubeedge_arch.png\" width = \"85%\" align=\"center\">\n\u003C\u002Fdiv>\n\n### In the Cloud\n- [CloudHub](https:\u002F\u002Fkubeedge.io\u002Fen\u002Fdocs\u002Farchitecture\u002Fcloud\u002Fcloudhub): a web socket server responsible for watching changes at the cloud side, caching and sending messages to EdgeHub.\n- [EdgeController](https:\u002F\u002Fkubeedge.io\u002Fen\u002Fdocs\u002Farchitecture\u002Fcloud\u002Fedge_controller): an extended kubernetes controller which manages edge nodes and pods metadata so that the data can be targeted to a specific edge node.\n- [DeviceController](https:\u002F\u002Fkubeedge.io\u002Fen\u002Fdocs\u002Farchitecture\u002Fcloud\u002Fdevice_controller): an extended kubernetes controller which manages devices so that the device metadata\u002Fstatus data can be synced between edge and cloud.\n\n\n### On the Edge\n- [EdgeHub](https:\u002F\u002Fkubeedge.io\u002Fen\u002Fdocs\u002Farchitecture\u002Fedge\u002Fedgehub): 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.\n- [Edged](https:\u002F\u002Fkubeedge.io\u002Fen\u002Fdocs\u002Farchitecture\u002Fedge\u002Fedged): an agent that runs on edge nodes and manages containerized applications.\n- [EventBus](https:\u002F\u002Fkubeedge.io\u002Fen\u002Fdocs\u002Farchitecture\u002Fedge\u002Feventbus): a MQTT client to interact with MQTT servers (mosquitto), offering publish and subscribe capabilities to other components.\n- [ServiceBus](https:\u002F\u002Fkubeedge.io\u002Fen\u002Fdocs\u002Farchitecture\u002Fedge\u002Fservicebus): an HTTP client to interact with HTTP servers (REST), offering HTTP client capabilities to components of cloud to reach HTTP servers running at edge.\n- [DeviceTwin](https:\u002F\u002Fkubeedge.io\u002Fen\u002Fdocs\u002Farchitecture\u002Fedge\u002Fdevicetwin): responsible for storing device status and syncing device status to the cloud. It also provides query interfaces for applications.\n- [MetaManager](https:\u002F\u002Fkubeedge.io\u002Fen\u002Fdocs\u002Farchitecture\u002Fedge\u002Fmetamanager): the message processor between edged and edgehub. It is also responsible for storing\u002Fretrieving metadata to\u002Ffrom a lightweight database (SQLite).\n\n## Kubernetes compatibility\n\n|                        | Kubernetes 1.27 | Kubernetes 1.28 | Kubernetes 1.29 | Kubernetes 1.30 | Kubernetes 1.31 | Kubernetes 1.32 |\n|------------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|\n| KubeEdge 1.19          | ✓               | ✓               | ✓               | -               | -               | -               |\n| KubeEdge 1.20          | +               | ✓               | ✓               | ✓               | -               | -               |\n| KubeEdge 1.21          | +               | ✓               | ✓               | ✓               | -               | -               |\n| KubeEdge 1.22          | +               | +               | ✓               | ✓               | ✓               | -               |\n| KubeEdge 1.23          | +               | +               | +               | ✓               | ✓               | ✓               |\n| KubeEdge HEAD (master) | +               | +               | +               | ✓               | ✓               | ✓               |\n\nKey:\n* `✓` KubeEdge and the Kubernetes version are exactly compatible.\n* `+` KubeEdge has features or API objects that may not be present in the Kubernetes version.\n* `-` The Kubernetes version has features or API objects that KubeEdge can't use.\n\n## Guides\n\nGet started with this [doc](https:\u002F\u002Fkubeedge.io\u002Fen\u002Fdocs).\n\nSee our documentation on [kubeedge.io](https:\u002F\u002Fkubeedge.io) for more details.\n\nTo learn deeply about KubeEdge, try some examples on [examples](https:\u002F\u002Fgithub.com\u002Fkubeedge\u002Fexamples).\n\n## Roadmap\n\n* [2024 Roadmap](https:\u002F\u002Fgithub.com\u002Fkubeedge\u002Fcommunity\u002Fblob\u002Fmaster\u002Froadmap.md)\n\n## Meeting\n\nTechnical Steering Committees (TSC) Meeting:\n- Pacific Time: **Wednesdays at 10:00-11:00 Beijing Time** (biweekly, starting from Feb. 26th 2020).\n([Convert to your timezone.](https:\u002F\u002Fwww.thetimezoneconverter.com\u002F?t=10%3A00&tz=GMT%2B8&))\n\nRegular Community Meeting:\n- Europe Time: **Wednesdays at 16:00-17:30 Beijing Time** (weekly, starting from Feb. 19th 2020).\n([Convert to your timezone.](https:\u002F\u002Fwww.thetimezoneconverter.com\u002F?t=16%3A30&tz=GMT%2B8&))\n\nResources:\n- [Meeting notes and agenda](https:\u002F\u002Fdocs.google.com\u002Fdocument\u002Fd\u002F1Sr5QS_Z04uPfRbA7PrXr3aPwCRpx7EtsyHq7mp6CnHs\u002Fedit)\n- [Meeting recordings](https:\u002F\u002Fwww.youtube.com\u002Fplaylist?list=PLQtlO1kVWGXkRGkjSrLGEPJODoPb8s5FM)\n- [Meeting link](https:\u002F\u002Fzoom.us\u002Fj\u002F4167237304)\n- [Meeting Calendar](https:\u002F\u002Fcalendar.google.com\u002Fcalendar\u002Fembed?src=8rjk8o516vfte21qibvlae3lj4%40group.calendar.google.com) | [Subscribe](https:\u002F\u002Fcalendar.google.com\u002Fcalendar?cid=OHJqazhvNTE2dmZ0ZTIxcWlidmxhZTNsajRAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ)\n\n## Contact\n\nIf you need support, start with the [troubleshooting guide](https:\u002F\u002Fkubeedge.io\u002Fen\u002Fdocs\u002Fdeveloper\u002Ftroubleshooting), and work your way through the process that we've outlined.\n\nIf you have questions, feel free to reach out to us in the following ways:\n\n- [mailing list](https:\u002F\u002Fgroups.google.com\u002Fforum\u002F#!forum\u002Fkubeedge)\n- [slack](https:\u002F\u002Fkubeedge.io\u002Fdocs\u002Fcommunity\u002Fslack)\n- [twitter](https:\u002F\u002Ftwitter.com\u002Fkubeedge)\n\n## Contributing\n\nIf you're interested in being a contributor and want to get involved in\ndeveloping the KubeEdge code, please see [CONTRIBUTING](.\u002FCONTRIBUTING.md) for\ndetails on submitting patches and the contribution workflow.\n\n## Security\n\n### Security Audit\n\nA 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.\n\n- [Security audit](https:\u002F\u002Fgithub.com\u002Fkubeedge\u002Fcommunity\u002Fblob\u002Fmaster\u002Fsig-security\u002Fsig-security-audit\u002FKubeEdge-security-audit-2022.pdf)\n\n- [Threat model and security protection analysis paper](https:\u002F\u002Fgithub.com\u002Fkubeedge\u002Fcommunity\u002Fblob\u002Fmaster\u002Fsig-security\u002Fsig-security-audit\u002FKubeEdge-threat-model-and-security-protection-analysis.md)\n\n### Reporting security vulnerabilities\n\nWe encourage security researchers, industry organizations and users to proactively report suspected vulnerabilities to our security team (`cncf-kubeedge-security@lists.cncf.io`), the team will help diagnose the severity of the issue and determine how to address the issue as soon as possible.\n\nFor further details please see [Security Policy](https:\u002F\u002Fgithub.com\u002Fkubeedge\u002Fcommunity\u002Fblob\u002Fmaster\u002Fteam-security\u002FSECURITY.md) for our security process and how to report vulnerabilities.\n\n## License\n\nKubeEdge is under the Apache 2.0 license. See the [LICENSE](LICENSE) file for details.\n","KubeEdge 是一个基于 Kubernetes 的边缘计算框架，旨在将容器化应用编排和设备管理扩展到边缘节点。其核心功能包括通过标准的 Kubernetes API 管理边缘应用与设备、确保云边可靠协作以在不稳定网络中无损传递消息、以及支持边缘自治运行。此外，KubeEdge 还提供了一个轻量级的边缘代理（EdgeCore），适用于资源受限的边缘环境。该项目非常适合需要在边缘侧执行复杂任务如机器学习、图像识别等场景，并且能够显著提升响应速度并保护数据隐私。作为 CNCF 毕业项目之一，KubeEdge 为构建云端与边缘端之间的高效协同提供了坚实的基础。","2026-06-11 03:25:22","top_topic"]