The Challenges of Maintaining an Edge Deployment at Scale – and How StarlingX Solves Them
summary
StarlingX upgrades its control plane first then orchestrates edge subclouds to upgrade themselves, staging images to local repos for air‑gapped sites and updating bundled applications before bumping Kubernetes so tenant workloads see minimal disruption. The project swaps Armada for Flux CD, migrates from CentOS to Debian and uses OSTree plus mount‑bind tricks to switch Kubernetes versions, supports single‑node to rack scale and is tested to 1,000 subclouds with up to 500 simultaneous updates, with partial rollback paths.
AI-written summary · about
chapters (7)
- 0:00Introduction to StarlingX
- 4:40System Controller Overview
- 5:56Upgrade Process and Workflow
- 11:40Edge Deployment Challenges
- 15:39Flock Services Upgrades
- 24:43How to Get Involved
- 26:23Q&A Session
related talks
42mThe Challenges and Solutions of Open Edge Infrastructures
16mMaking a better world by edge computing infrastructure: the experience and thinking from FiberHome
39mStrangling the Legacy with Kubernetes
07mKeynote: Pushing the Boundaries of Open Source for a Brand New Edge
46mAdaptive cloud approach: Build and scale apps from cloud to edge
07mScalable Edge Data Centers: Current Challenges and How to …
24mThe Cluster Is Not the Platform: Operating Industrial Edge Kubernetes as a Fleet
05mScaling Kubernetes Deployment at the Edge with Argo and More