From Containers to Kubernetes Operators
summary
Docker images land around 750 MB and move to trimmed CentOS7/UBI bases (~600 MB) to reduce false positives; images are immutable and no latest tag is allowed so deployments pin minor and patch versions. Docker Compose stays for demos; Helm charts are GA for production. A Kubernetes operator (v1.2.1, 1.3 imminent) runs a reconciliation loop, operator drains nodes before removal, auto-generates TLS and secrets, and is tested on GCP/Azure/AWS/Openshift — it encodes upgrade and day‑two operations.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 4:55Docker fallacies
- 7:54Latest
- 10:37Runtime Mutation
- 12:34Base Images
- 13:43Base Image Size
- 16:17Universal Base Images
- 20:49YAML
- 27:37Operators
- 38:20Elastic Surge
- 41:46Deployment Options
- 45:14Kubernetes Paradox
related talks
45mFrom Containers to Kubernetes Operators
44mFrom containers to Kubernetes operators
46mAround & After Kubernetes: The Principles and Ideas that Guide Us
01h 02mContainers in Production: It’s Like Orchestrating Cats
42mImproving Containers Isolation in Kubernetes
01h 06mSo many Docker platforms, so little time...
38mKompose: The Docker-Compose of Kubernetes
22mMaking Kubernetes How We Build Things
