DevOps at the Edge - Why and How to Adopt These Practices for the New Cloud?
summary
Explains why Edge infrastructure should follow DevOps principles but use different operational patterns to handle limited resources, unreliable networks and thousands of remote sites. Recommends containerization and Kubernetes-based tooling (OpenShift and microShift), multi-cluster fleet management and projects like flota, and concrete practices such as zero-touch provisioning, CI/CD adapted for constrained nodes, autoscaling/rebalancing for failures, and measurable deployments to keep large numbers of Edge sites consistent and secure.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:22Edge Computing definition
- 8:41Why Edge now
- 14:19Edge use cases
- 21:44ML and data at Edge
- 24:31Edge technical challenges
- 31:56DevOps for Edge
- 38:05Edge deployment tools
- 42:58Red Hat Edge vision
- 43:20Conclusion
related talks
10mDevOps on the Edge!
08mDefining the 'edge' in edge computing
29mDevOps in containerized world
30mDevOps In A Cloud Native World
31mWhat it Really Takes to be Successful at the Edge
50mIs it ODD to shift left? Becoming elite DevSecOps performers
43mDevOps in Cloud
44mDevOps for developers (or maybe against them?!)