GitOps in the Real World: Opportunities for Developer Experience Improvement
summary
Chick‑fil‑A runs GitOps at production scale: Kubernetes on EKS with Argo CD syncing an atlas repo of merged manifests; CI uses GitHub Actions and Artifactory, monitoring with Prometheus/Grafana/Thanos, and traffic replay with SpeedScale. Platform handles about 300k requests per minute peak (120k/min average, ~330M daily) and thousands of commits and hundreds of PRs daily. The claim: GitOps works at scale but UX fails when developers must hand‑edit YAML, so they build manifest templates, overlays and UI/IDE flows that push validated changes as pull requests.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:24Who is Chick-fil-A?
- 1:18Traffic Overview
- 2:14Developer Overview
- 3:10Architecture Overview
- 4:22Chick-fil-A's Application Platform (CAP)
- 8:50Deployment Process - Simple Version
- 9:18Pain Points
- 11:20Example: ArgoCD UI
- 12:50Proposed Solutions
related talks
47mGitOps - Using Git as your source of truth for build, deploy and observability
43mGitOps at Scale with and Argo CD on
35mGitOps - the holy grail of devops
35mGitOps - Operations by Pull Request
13mHow GitOps Should I Be? Lessons from a Kinda-GitOps Environment
29mThe Evolution of GitOps in Platform Engineering
45mGitops: The Kubernetes way
06mGitOps - At a Glance