Approach to GitOps — Achievements, Mistakes and Lessons Learned
summary
A GitOps pipeline used three years in production to manage many microservices across dozens of environments, built with Terraform, Docker, Kubernetes, Helm, Nexus, GitLab and internal tools. Explains concrete artifacts: a public‑key wrapping secrets service, repo layout conventions, Helm chart validation tests, an API to auto‑generate secrets, and a visualization/dashboard. Reports real failures such as manual secret churn and slow builds, the fixes tried, and which fixes actually reduced operational toil.
AI-written summary · about
chapters (8)
- 0:00GitOps introduction
- 3:41Monolith to microservices
- 8:21Octopus config system
- 12:50Scaling challenges
- 17:53Secrets management
- 21:12GitOps tools comparison
- 23:43GitOps best practices
- 30:21Q&A
related talks
23mA Tall Tale of GitOps
02h 02mAn end-to-end GitOps Architecture: Terraform, Ansible, Kubernetes and AWS
55mGitOps, Fostering Next-Generation Operations Teams
43mHow GitOps Enabled Us to Answer an Unanswerable Question
45mGitops: The Kubernetes way
47mGitOps - Using Git as your source of truth for build, deploy and observability
35mGitOps - the holy grail of devops
36mGitOps: The Single source of truth
