Navigating the Shift to GitOps: Overcoming Challenges in Migrating from Jenkins..
summary
Three practical migration patterns with tradeoffs and a surprising adoption stat: about 50% of Argo CD users enable progressive rollouts. Option one adds Argo Rollouts to Jenkins deploys for blue/green or canary with automated verification and no GitOps drift detection. Option two keeps Jenkins for CI and uses an image-updater to commit image changes, letting Argo CD handle syncs. Option three moves pipelines into Argo Workflows, which run as Kubernetes jobs (parallel by default), changing scaling, secrets, and ops models.
AI-written summary · about
chapters (8)
- 0:00Migrating from Jenkins to GitOps
- 1:44Why move from Jenkins
- 3:07Argo CD and GitOps benefits
- 4:32Argo Rollouts for progressive deployments
- 7:02Jenkins with Argo CD migration
- 9:27Pipelines to Argo Workflows
- 12:20Migration strategies and benefits
- 14:29Q&A on savings and experiences
related talks
43mGitOps at Scale with and Argo CD on
27mImplementing GitOps with ArgoCD: A Practical Guide
25mMigrating CI/CD from Jenkins to Argo
40mHow GitOps Changes Everything in CI/CD
29mCombining Progressive Delivery with GitOps and Continuous Delivery
29mDemystifying Gitops with ArgoCD
30mThe Objectives And The Principles Behind GitOps
46mFrom FTP to ArgoCD & Argo Rollouts: An adoption history inside a corp