The GitOps Paradox: Why Your Devs Need an API You Don't Want To Build - Simon Koudijs
summary
Platform teams expose a small Kubernetes control plane as a typed API-first front door (not a replacement for Git) and use CRDs as the declarative surface; an open-source operator called gitops-reverser translates those high-level CRs into clean Git commits and pull requests, preserving review and auditability. The prototype uses KRM/KO, Flux (or ArgoCD), and can hand off exploded production manifests to Crossplane or KRO; the live demo produces real commits, merges, and deployments and the runtime operator itself avoids AI.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:47Vision and prototype demo
- 5:21Live reverse GitOps demo
- 9:38Kubernetes API as front door
- 13:08Right abstraction for platform teams
- 14:52Deploying pot info app
- 18:43Feedback and discussion
- 19:47Q&A
related talks
15mGitOps in the Real World: Opportunities for Developer Experience Improvement
19mGitOps 101: Demystifying GitOps
19mCrossing the Divide: How GitOps Brought AppDev & Platform Teams Together!
23mA Tall Tale of GitOps
31mPanel Discussion: GitOps & Best Practices for Cloud Native CI/CD
31mWhen GitOps Meets UX
24mFrom Kubernetes to PaaS to Developer Control Planes
57mBring the API culture to DevOps teams