Containerization crossroads: Experiences-Experiments-Expectations
summary
Container usage history, Docker and Kubernetes practices, and concrete fixes for runaway images land as actionable takeaways: a problematic image grows to 2.3 GB; fixes include using lightweight base images, ordering Dockerfile steps to leverage cache, .dockerignore, combining RUN lines and multi-stage builds to copy only artifacts. Security measures: image scanners, non-root users, read-only filesystems and seccomp; Kubernetes specifics: CPU/memory/ephemeral limits, requests, affinities, pod disruption budget, liveness/readiness probes, HPA/VPA tradeoffs, and Helm for packaging.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:52A BRIEF HISTORY AROUND CONTAINERIZATION
- 2:06CONTAINERS
- 4:42CONTAINER BUILD TIME PRINCIPLES
- 5:54CONTAINER RUN TIME PRINCIPLES
- 9:25BIG DOCKER IMAGE(S)
- 13:11SLIMMING BIG DOCKER IMAGES - BONUS
- 15:36SECURITY OBSERVATIONS
- 17:47RESOURCE MANAGEMENT
- 20:00HIGH AVAILABILITY/ SCALABILITY
- 21:57DOCUMENTATION AND TESTING
related talks
26mContainerization War Stories
43mContainer Security: So Many Options, Use Them All!
18mPractical End-to-End Container Security at Scale
47mContinuous Delivery with Containers: The Good, Bad, & Ugly
40m"Willy Wonka and the Secure Container Factory"
30mMaster the Container Security Model with
01h 00mContainer Usage Patterns
34mWhat We Learned Dissecting the World's Most Popular Containers