Top 5 container and Kubernetes best practices
summary
Five concrete practices: use small multistage images (Alpine example—700 MB vs 65 MB speeds pulls and avoids pending pods), organize by namespaces with per-namespace resource profiles, implement readiness and liveness probes (synthetics suggested) and surface probe failures in an events timeline, set CPU/memory requests and limits and wire warnings to alerts (News UK sees warnings ~90 minutes before memory violations), and ingest logs into an observability platform (New Relic, CloudWatch) to correlate pod, container and application faults.
AI-written summary · about
chapters (20)
- 0:00Intro
- 0:42Meet Gracie Andrews
- 2:00Containers and Kubernetes
- 4:13Kubernetes adoption
- 5:32Kubernetes best practices
- 6:39Top 5 best practices
- 7:41Build small container images
- 8:50Why use smaller images
- 10:31Layers
- 11:57Observability
- 16:06Names
- 18:43Resource allocation
- 22:39Health checks
- 25:30liveliness probes
- 27:24events timeline
- 29:24requests and limits
- 32:04alerts
- 35:09contextualizing
- 37:34logs
- 40:24Recap
related talks
45mKube Me This! Kubernetes Ideas and Best Practices
19mKube Me This! Kubernetes Ideas and Best Practices
51mBest Practices to Spring to Kubernetes Easier and Faster
28mRunning Microservices on Kubernetes – Best Practices
36mKubernetes Confessions: Real Mistakes We’ve All Made (and What They Teach Us)
26mContainerization crossroads: Experiences-Experiments-Expectations
45mTroubleshooting containerized applications
05mLightning Talk: 7 Tips for Tricks to Enjoy Your Kubernetes Journey