All 28 GitOps Principles questions
More in GitOps Principles
How do you handle non-Kubernetes resources in a GitOps model? How does GitOps improve developer experience? What role do webhooks play in GitOps with ArgoCD? How do you structure Git repositories for GitOps at scale? How does GitOps support disaster recovery? What are the trade-offs and limitations of GitOps? How do you promote changes across environments in GitOps? What are common anti-patterns in GitOps? How do you validate manifests before they reach the cluster (policy as code)? How do you separate application code repos from configuration repos, and why?
Advertisement
Back to results for “Sync & Health”
ArgoCD › GitOps Principles

What is the reconciliation loop and how often does ArgoCD run it?

Advanced

Answer

The reconciliation loop continuously compares desired (Git) vs live (cluster) state and acts on differences. ArgoCD polls Git on an interval (default ~3 minutes) and can react instantly to webhooks; it also watches cluster resources. Reconciliation computes the diff, updates sync/health status, and applies changes if auto-sync is enabled.
# argocd-cm: change polling interval
data:
  timeout.reconciliation: 180s
Real-world example A Git webhook triggers ArgoCD to reconcile immediately on merge instead of waiting for the next poll cycle.

Common follow-ups: How do webhooks speed reconciliation? | What does the loop compare?

Sync & Health Applications GitOps Principles
All 28 GitOps Principles questions