Microservice Continuous Delivery
summary
Claims concrete: Kubernetes and Helm plus container-based steps and reusable OCI images let each pipeline step run in its own environment; a single shared CI pipeline with per-repo triggers replaces thousands of copy‑paste pipelines; a local SSD cached volume speeds IO so a customer cuts builds from 1.5 hours to 12 minutes. Tools shown: Codefresh runner, Helm charts, Argo CD, Terraform steps, Docker/OCI images, Jenkins as legacy. Deployment testing uses canary deployment verification and generated manifest repos; demos and customer cases show it works.
AI-written summary · about
chapters (20)
- 0:00Intro
- 1:05Why microservices
- 4:07Challenges
- 5:47Learnings
- 6:30Traditional Pipelines
- 7:34Scalability
- 8:13Shared Libraries
- 8:46Problems with Shared Libraries
- 10:11Our Approach
- 10:34Our Architecture
- 11:36Containerbased pipelines
- 13:26Open source steps
- 14:00Single pipeline with context
- 15:21Flexible pipeline execution
- 16:14Demo
- 20:25Deployment verification
- 22:31Summary
- 27:27Security
- 28:50QA
- 31:17Hardware requirements
related talks
40mMicroservice Continuous Delivery
30mModern Continuous Delivery
37mDesigning Cloud Ready Applications
47mContinuous Delivery Meets OpenShift
28mContinuous Integration Testing: Fully Test your Microservices Application, Early and Often
41mAll Things Continuous
01h 03mYet Another Continuous Delivery Talk
24mYour CI Pipeline is the Platform