Kubernetes IoT and Edge Working Group
summary
Survey of options for running Kubernetes at constrained sites: deploy full clusters at each site, run a central control plane managing lightweight edge nodes, or use proxy node implementations. Concrete tools and behaviors noted: k3s replaces etcd with SQLite and swaps Docker for containerd, bundles Flannel/CoreDNS/Traefik and runs on nodes with <4GB RAM; virtual kubelets proxy pod specs to leaf devices; Azure IoT Edge now has a Kubernetes-based preview; Eclipse Ditto digital twin and HawkBit OTA for millions target intermittent connectivity and firmware updates. Biweekly working-group meetings maintain links, demos and a white paper.
AI-written summary · about
chapters (10)
- 0:00Start
- 1:39Standard Kubernetes Architecture
- 3:44Option 2: central Kubernetes control plane managing edge
- 6:38Differentiating factors
- 8:24Whole clusters, with control plane, at edge
- 9:31Rancher K3
- 15:40Azure lot Edge (preview) - Kubernetes clusters at edge
- 23:22Eclipse Hono
- 24:37Eclipse Ditto
- 25:44Eclipse howBit
related talks
34mKubernetes IoT and Edge Working Group
01h 16mIntro + Deep Dive: Kubernetes IoT Edge WG
20mKubernetes at the Edge
01h 01mDo We Really Need Kubernetes at the Edge
36mUsing Kubernetes in IOT Edge Node Development
36mEdge Computing in Kubernetes: Best Practices for the Future
34mManaging Edge Nodes With “KubeEdge”
39mShould You Bring Kubernetes on Your Edge Roadtrip?
