Extending clusters to the edge and far edge with bootable containers
summary
Combines virtual kubelet and bootc to run native workloads on resource-constrained edge devices without a kubelet or container engine, using an edge agent plus a RabbitMQ cluster for event-driven control; images are built with bootc image-builder into QCOW/ISO/AMI artifacts, deployed initially by booting a discovery image, then the agent handles switch/rollback and updates; one virtual kubelet instance can manage many devices (avoids 5,000-node limit), and the demo shows successful image fetch and boot.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:02Project Peter Code
- 2:05Edge architectures
- 3:52Scheduling challenges
- 4:55Virtual Kubelet and BootC
- 6:40Virtual Kubelet in Kubernetes
- 7:01Bootable containers
- 8:24Bootable containers benefits
- 9:30BootC container file
- 10:39BootC image conversion
- 11:00Kubelet solution architecture
- 12:03Cluster and developer workflows
- 14:30Developer workflow with BootC
- 15:35Live demo
- 17:47Q&A session part one
- 18:50Q&A session part two
- 20:17Future extensions
- 21:44Q&A 3 and conclusion
related talks
25mIntroduction to Bootable Containers
10mKubernetes: Enabling Edge Workloads
23mFrom Disk Images To Container Images: Deploying Bootc To Bare Metal With Kubernetes an...
34mKubeEdge: Kubernetes Native Edge Computing Framework
34mManaging Edge Nodes With “KubeEdge”
05mWhat's Exciting Now In Bootc, And What's Next?
35mKubeEdge – Kubernetes Native Edge Computing Framework
20mKubernetes at the Edge