Separation of Orchestration and Computation in KubeEdge, Understand the Why and How
Talkat Kubernetes on Edge Day Europe 2022 · on Tuesday, 2022-05-17· at 14:10· Pavilion 4, Room C | Level 2 | Central Forum·
summary
KubeEdge splits orchestration to the cloud and computation to the edge by running cloudcore controllers and a lightweight edgecore agent; it uses cloudhub/edgehub websocket tunnel for bi‑directional sync, an edged (~70MB) reworked kubelet, and a SQLite node-level datastore so edge nodes continue working offline. Device communication uses Mosquitto (publish/subscribe) and multiple CRIs (docker, containerd); setup follows kubeadm init/join with certs and kubeconfig and is reported to scale to millions of devices.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 0:58About Harshita
- 1:59About KubeEdge
- 4:23Initial Challenges
- 6:19KubeEdge Architecture
- 9:01KubeEdge Components
- 12:59Cloud Components
- 16:17Data Distribution
- 16:49Cubelet
- 17:51EdgeCon Controller
- 18:55Communication
- 21:04Quick Start
- 22:37Cubeconfig
- 23:36Edge Core
- 24:45Device Management
- 25:09Conclusion
related talks
31mIntro to KubeEdge: Kubernetes Native Edge Computing Framework
35mKubeEdge – Kubernetes Native Edge Computing Framework
34mManaging Edge Nodes With “KubeEdge”
34mKubeEdge: Kubernetes Native Edge Computing Framework
41mKubeEdge
33mKubeEdge: From Fixed Location to Movable Edge, Latest Updates and...
20mKubernetes at the Edge
26mIntro to KubeEdge: Kubernetes Native Edge Computing Framework