Kubernetes at the Edge
summary
Edge deployments use two concrete approaches: KubeEdge extends Kubernetes with a lightweight edge agent (hd), a message bus, meta-management, device-stream and event-bus to keep metadata local and enable offline autonomy, while k3s ships a trimmed Kubernetes (server + agent), swaps etcd for SQLite, removes nonessential controllers and gives a tiny installer. A community survey shows about 30% run full clusters at the edge and 30% keep control planes in the cloud with agents at the edge. Trade-offs: ARM/low‑CPU limits, offline sync vs. per‑edge control planes.
AI-written summary · about
chapters (10)
- 0:00Introduction to speakers
- 0:23What is edge computing
- 2:11Kubernetes at the edge
- 5:22Problems deploying Kubernetes at edge
- 8:13KubeEdge solution overview
- 12:30KubeEdge architecture
- 12:51K3s for edge computing
- 16:48K3s deployment model
- 18:13Other edge Kubernetes options
- 18:57Summary and future
related talks
34mManaging Edge Nodes With “KubeEdge”
34mKubeEdge: Kubernetes Native Edge Computing Framework
31mIntro to KubeEdge: Kubernetes Native Edge Computing Framework
35mKubeEdge – Kubernetes Native Edge Computing Framework
36mEdge Computing in Kubernetes: Best Practices for the Future
01h 01mDo We Really Need Kubernetes at the Edge
39mShould You Bring Kubernetes on Your Edge Roadtrip?
41mKubeEdge