What the Diff?
summary
Explains how Argo CD actually detects drift: the default legacy client-side three‑way diff uses last-applied-configuration, while the server-side diff does a dry‑run apply, relies on Kubernetes field managers and is currently a beta feature; structured‑merge diff leverages Kubernetes’ structured merge library. Shows that mixing client‑side apply with server‑side diff produces missed changes, how to enable server side via controller.diff.serverSide=true or per‑app annotation, and when to use respect-ignore-differences or include-mutation-webhook to avoid noisy out‑of‑sync states.
AI-written summary · about
chapters (6)
- 0:00Introduction to diffing
- 5:13Diffing strategies
- 6:40Challenges in reconciliation
- 18:24Managing differences
- 18:46Best practices
- 19:44Q&A session
related talks
29mHow to Preview and Diff Your Argo CD Deployments
28mArgo CD Maintainer's Panel
39mSolving configuration drift using GitOps and ArgoCD
38mDIFFY Catching Bugs without Writing Tests
36mkubectl apply, and The Dark Art of Declarative Object Management
31mTouch Base: How I Broke Business Applications Deployment
38mDiffy - Predicting and Preempting Regressions in Services - Puneet Khanduri & Prashant Khanduri
05mProject Lightning Talk: Argo CD at Scale: 5 Features You Should Not Miss!