Deploying to Kubernetes Thousands of Times Per/Day
summary
Claims delivery pipelines support thousands of Kubernetes deployments per day by treating images as immutable release artifacts tied to git, running automated builds that attach commit metadata, and enabling instant time travel rollbacks to the exact image and commit. The stack runs shifted-left integration and performance tests in ephemeral feature-branch environments (Helm charts define full stacks), uses readiness/liveness probes and canary updates to avoid bad rollouts, and outsources cluster lifecycle to autoscaling cloud or a dedicated ops team.
AI-written summary · about
chapters (33)
- 0:00Introduction
- 0:21High Velocity Teams
- 1:07Why Choose Communities
- 2:38Reduce Risk
- 5:30Center on Images
- 5:52Immutable
- 8:07Carry the History
- 10:28Shift Left
- 11:08Dev Release Process
- 11:46Cost Sink
- 12:16Shift Left Pipeline
- 13:30Portable Application
- 13:52Disaster Recovery
- 16:26Configuration
- 17:18Application portability
- 17:34Cloud vs Kubernetes
- 19:01Kubernetes open standards
- 19:29Certifications
- 19:43Connect all the dots
- 20:34Codefresh
- 22:25Security Changes
- 23:25Commit Changes
- 24:48Scalable Architecture
- 25:53Live on Stage
- 26:28Release
- 28:02View
- 28:19Performance Tests
- 29:23Why High Velocity
- 29:50Google Cloud Platform
- 30:42Questions
- 34:04MultiCloud
- 41:01Secrets
- 46:40Node Scaling
related talks
37mDesigning Cloud Ready Applications
38mScaling Kubernetes Deployments Across +15'000 Namespaces
22m10 Kubernetes is hard!
29mOrchestrating 10,000+ Kubernetes deployments with 1 pipeline
33mA Day in the Life of Kubernetes Release with Tools, Challenges, and Operations
52mFrom 0 to Continuous Deployments with Kubernetes, Helm and GitLab
26mOrchestrating 10,000+ K8s deployments with 1 pipeline
46mBlue-green Deployments, A/B Testing, and Canary Releases on Kubernetes