What it Really Takes to be Successful at the Edge
summary
Claims that large-scale edge needs a full automation foundation are backed by concrete choices: Ansible for infrastructure-as-code, podman/kubernetes for containers, VS Code code‑ready workspaces for consistent dev environments, ACME for cert automation, and OSTree/greenboot for safe OS updates. The build surfaces include APIs, a service catalog, CI/CD pipelines, PKI with automated cert rotation (hundreds of thousands of certs), unified observability and SRE practices. Implementation takes years not weeks (about 5–6 years) to reach reliable deployment across 5,000+ devices and it succeeds when repeatable automation replaces one-off tickets.
AI-written summary · about
chapters (9)
- 0:00Welcome
- 1:02Edge success beyond apps
- 3:50Edge infrastructure foundation
- 9:08Edge networking and security
- 10:32Infrastructure to business value
- 13:58Automate Edge deployments
- 20:16Edge observability and reliability
- 23:17Edge device recovery
- 26:05Q&A
related talks
10mDevOps on the Edge!
45mDevOps at the Edge - Why and How to Adopt These Practices for the New Cloud?
01h 02mTools and Techniques for Infrastructure as Code
29mHunting the DevOps Whale
15mPlatform Engineering - About Tools...
30mMoving beyond DevOps with automated cloud-native platforms
53mGround Truths of a Rugged DevOps Practitioner
32mHow to win at platform engineering