Scale your CI/CD setup for Cloud Native Microservices via InnerSource
summary
Enterprises report pipeline sprawl across thousands of teams and propose a concrete fix: publish standardized CI templates from a central DevOps Dojo repository so teams clone and tweak instead of rebuilding pipelines. CI builds container images, stores them in a registry (example Azure Container Registry), and CD deploys to Kubernetes clusters; Docker and k8s are named as the compute stack. InnerSource collaboration opens those templates company‑wide so a 5‑person team can leverage a 350,000‑developer workforce to scale fixes.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 3:48Strategic vision over tactics
- 8:43Microservices basics
- 13:22Cloud native apps
- 16:56Standardization solves scale
- 20:43DevOps Dojo pipelines
- 22:49Open vs InnerSource
- 26:43Scaling CI/CD lessons
- 29:55Containers and Kubernetes
- 32:01Summary
related talks
36mAvoid Chaos in Our CI/CD Pipelines with Inner Source
16mContinuous Delivery and InnerSource - Why you Should be Doing Both
14mHow we manage over1500 git repo’s CI/CD with a full InnerSource solution
36mInnerSource at Scale: A Platform-centric Approach
28mScale Your DevOps Initiative Beyond Its Awkward Teenage Years
40mMicroservice Continuous Delivery
50mImplementing Cloud Native CI/CD
01h 00mVintage CI/CD. How and Where to Start