The hard part of GitOps at scale is not the sync engine. It is drift: everything that changes your cluster after Argo CD says it is in sync. If your first post on why LinkedIn outgrew Argo CD covered when the engine breaks, this covers the quieter failure -- the one that makes your Git repo lie...
Source: [Dev.to](https://dev.to/robust_true_try/the-drift-problem-that-breaks-gitops-at-scale-i99)