Lightning Talk: Continuous Delivery with Kubernetes: The Prequel

on YouTube ↗07m

" summary

GitLab moves to continuous delivery on legacy VMs with Ansible and GitLab CI/CD rather than Kubernetes, achieving commit-to-canary two hours (down from over a day), shifting from weekly to daily deploys and hitting 24 releases in July vs 4 in May. Developers enter an on-call rotation in three weeks, automated test failures block progression and reduce hotpatching, and the effort prioritizes culture and workflow changes first so the team can later migrate to Kubernetes without disrupting delivery.

AI-written summary · about

" chapters (4)

1. 0:00Start
2. 0:52Primer
3. 2:07Gitlab Case Study of Moving to Continuous Delivery
4. 2:40Why Do We Care about Continuous Delivery

" related talks

• 01h 01mContinuous Delivery with GitLab CI and KubernetesMichael Harrer · DevOpsCon 2017 Berlin
• 54mFrom Code to CustomerTobias Mende · NDC Porto 2024
• 43mCONTINUOUS DELIVERY: Five Years OnGiovanni Toraldo · Incontro DevOps Italia 2018
• 30mJourney To The CloudEric Labourdette, Vince Stammegna · GitLab Commit San Francisco 2020
• 36mCI/CD BoF: Delivering Quality QuicklyBrice Fernandes, Marc Carré · KubeCon + CloudNativeCon Europe 2018
• 55mCI/CD Best Practices with Kubernetes and GitLabDmitriy Stolyarov · HighLoad++ 2017
• 10mLightning Talk: Day 2 Has Arrived - How Carvel Suite and Cluster API Can Bring GitOps to Your Kubernetes InfrastructurePietro Terrizzi · GitOpsCon Europe 2022
• 30mOur Continuous Delivery JourneySuzie Prince · DevOpsDays Kansas City 2016