DevOps in a containerized world
summary
Argues DevOps becomes more necessary with containers, not obsolete, because containers force clear separation of concerns between application and infrastructure and require API-driven, hands‑off platforms. Recommends automation, git‑based CI/CD (used with Docker CI at a Berlin customer that exposed a registry storage bug after ~one week of testing), metrics/health checks, secrets management, RBAC tokens and network plugins (Flannel/Calico) and runtime choices (Docker/CRI‑O). Warns that giving Docker CLI is effectively root and that resource limits prevent whole‑host OOMs.
AI-written summary · about
chapters (14)
- 0:00Start
- 2:21Classical Devops
- 8:43Ci Cd System
- 10:09Devops Tool Chain
- 11:27Continuous Delivery
- 12:06The Learning Curve
- 15:28Infrastructure Developers
- 15:50Security Developer
- 19:35Software Defined Networking
- 25:26Benefits
- 37:53Container Orchestration
- 39:06Ingress and Egress
- 48:36Total Cost of Ownership
- 50:26Conclusions
related talks
44mContain yourselves
46mWhat Security People Want: Making DevSecOps Happen with Containers
47mContinuous Delivery with Containers: The Good, Bad, & Ugly
10mDevOps on the Edge!
50mIs it ODD to shift left? Becoming elite DevSecOps performers
41mDevOps for Java Developers (or maybe against them?!)
29mDevOps in containerized world
28mKeep Calm and DevOps in an Enterprise