Extending Cloud Native Boundaries! Bringing KubeEdge Workloads to AndroidOS
summary
KubeEdge runs on Android by patching the Android Linux kernel (namespaces, cgroups, overlayfs), disabling paranoid networking and adding iptables routes, then installing static containerd/docker binaries and mounting an SSD-backed overlay rootfs; the lightweight edge agent is ~70 MB lightweight KubeEdge agent. Network tunneling uses H mesh for unstable cloud-edge links. Demo shows Android devices registered in cloud and running pods, with successful container login from the cloud.
AI-written summary · about
chapters (9)
- 0:00Extending cloud native to AndroidOS
- 2:48KubeEdge community overview
- 9:15KubeEdge core concepts
- 11:50KubeEdge on AndroidOS challenges
- 14:43AndroidOS integration process
- 16:37Demo: Containers on AndroidOS
- 17:43Deploy KubeEdge to AndroidOS
- 18:45Future of KubeEdge on AndroidOS
- 19:27Q&A: Android framework access
related talks
39mExtending Cloud Native Boundaries! Bringing Cloud Native Workloads to...
31mIntro to KubeEdge: Kubernetes Native Edge Computing Framework
34mManaging Edge Nodes With “KubeEdge”
26mIntro to KubeEdge: Kubernetes Native Edge Computing Framework
33mKubeEdge: From Fixed Location to Movable Edge, Latest Updates and...
35mKubeEdge – Kubernetes Native Edge Computing Framework
34mKubeEdge: Kubernetes Native Edge Computing Framework
41mKubeEdge