Develop once, deploy anywhere: flexible infrastructure extends to the edge
summary
Edge use favors local processing for latency and control, but operational criteria decide whether to run Kubernetes: unknown or variable load or need for capacity/HA (multiple nodes) requires orchestration, while a single embedded unit with known stable load uses podman instead. Customers show hundreds or thousands of deployments from microcontroller devices with tens of kilobytes to high‑end servers; distribution choices emphasize rollbackable OS updates (rpm os3 and green boot), secure device onboarding and attestation, and app/operator tooling like cubework and metal cubed, Argo CD and Open Cluster Management.
AI-written summary · about
chapters (4)
- 0:00Start
- 2:09adopting edge computing
- 5:03run a clustering solution like kubernetes on a single node
- 6:05choosing a kubernetes distribution for your edge use
related talks
20mKubernetes at the Edge
39mShould You Bring Kubernetes on Your Edge Roadtrip?
36mEdge Computing in Kubernetes: Best Practices for the Future
05mScaling Kubernetes Deployment at the Edge with Argo and More
14mBorn in the Cloud growing at the Edge?
10mKubernetes: Enabling Edge Workloads
34mKubeEdge: Kubernetes Native Edge Computing Framework
01h 01mDo We Really Need Kubernetes at the Edge