A first-hand account of migrating from traditional CI/CD to GitOps at enterprise scale. The author details why configuration drift and compliance gaps forced the evaluation, how ArgoCD was chosen as the primary tool alongside Jenkins and GitHub Actions, and the phased rollout strategy starting with low-risk services. Key outcomes included deployment frequency jumping from weekly to multiple daily deployments, reduced lead times, and improved rollback reliability via Git reverts. The post also covers organizational resistance, the importance of training and templates, and lessons learned around secrets management and environment strategy.
Sort: