GitOps the Hard Way, with Argo CD

Limiting How Many Sync Records Argo CD Keeps

Every time Argo CD successfully syncs an Application, it appends an entry to that Application's sync history. Each entry records which Git revision (the commit SHA) was deployed and when. This history is what powers argocd app rollback: a rollback tells Argo CD to re-sync one of those earlier commits.

Note that this is not the same as a Kubernetes Deployment's revisionHistoryLimit, even though the field name is identical. The Deployment field controls how many old ReplicaSets the cluster keeps. The Argo CD field controls how many sync entries the Application keeps in its own status.history. They are unrelated.

By default Argo CD keeps 10 entries. You change that with the revisionHistoryLimit field, which sits directly under spec (not under spec.source):

apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: todo-app
  namespace: argocd
spec:
  destination:
    namespace: