The Kubernetes Hunger Games: Distro Performance in the Edge
summary
Benchmarks run on single-node 1 CPU / 2 GB Ubuntu 22.04 VMs use the Cloud‑Bulldozer Benchmark Operator plus iperf, CIS bench, stress, K‑bench (fio) and report concrete numbers: k3s shows 1 Gbps average network with spikes to ~2.4–2.7 Gbps and leads CPU/stress tests (528 vs k0s 363 vs microK8s 231) and memory copy; k0s wins file I/O and FIPS/security features; microK8s has the smallest runtime footprint and lowest K‑bench latency; k2d is a 20 MB Docker–Kubernetes API translator for tiny devices.
AI-written summary · about
chapters (17)
- 0:00Kubernetes at the Edge intro
- 0:43Why distros matter for Edge
- 2:29Open-source vs managed distros
- 3:34k3s, microK8s, k0s overview
- 6:48Benchmark setup and method
- 8:16Network throughput results
- 10:00CPU and I/O performance
- 12:50Stress test results
- 14:39Storage with K-Bench
- 17:50Resource footprint on devices
- 18:33k2d for ultra-small devices
- 19:59Talos OS overview
- 22:06CubeEdge for Edge workloads
- 23:09Choosing the right distro
- 24:56Security and isolation features
- 25:16Benchmark summary
- 26:45Q&A
related talks
41mRunning Kubernetes on Workstations and Edge / IoT Devices
48mScale and Performance Testing of Kubernetes: Answers for Specific Applications
23mMigrating 5G Core to the Edge, Wisely and Confidently with Kubernetes
19mKubevirt and the Cost of Containerizing VMs
02h 26mKubernetes Performance Tuning Workshop
01h 16mIntro + Deep Dive: Kubernetes IoT Edge WG
34mKubeEdge: Kubernetes Native Edge Computing Framework
31mLoad Testing Kubernetes: How to Optimize Your Cluster Resource Allocation in Production [I]