GitOps and the CD Pipeline - Friend or Foe?
summary
Claim: GitOps breaks the CD pipeline at scale unless the front end is automated. A microservice catalog like microservice catalog stores image tags, key/value config and owners, generates dozens of per-environment YAMLs (demo scenario: 15 YAML files from a few services), creates automated PR generation when a registry push happens, and can automate commits based on policies so the CD pipeline moves from manual pull-request steps to reproducible, policy-driven deployments.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:15Can GitOps Scale Microservice CD
- 0:42GitOps started with Containerized Apps
- 1:37One file branched per Environment
- 2:43OK Now Microservices
- 3:27We are going to have more than one Yaml
- 4:37And Now Add the Pipeline
- 5:17Emergence of the Microservice Catalog
- 7:20Evolving GitOps and CD
- 8:10A GitOps Pipeline
- 9:00Oh... and meet the Speaker
- 9:28Learn More About Catalogs
related talks
30mThe Intersection of CD Gates and GitOps: A Match Made in Deployment Heaven
36mGitOps: The Single source of truth
47mGitOps - Using Git as your source of truth for build, deploy and observability
40mHow GitOps Changes Everything in CI/CD
06mGitOps - At a Glance
33mGitOps Pipelines: Everything Everywhere All at Once
45mGitops: The Kubernetes way
57mPipelines: Everything Everywhere All At Once