Course contentsShow
← Cloud and Infrastructure
Lesson 1885 of 2,98940. ArgoCDFree lesson

Application Health and Sync Status

Understand how ArgoCD determines application health and synchronization state.

Application Health and Sync Status

You'll learn: How ArgoCD evaluates whether your application is healthy and synchronized with its Git source of truth.

Understanding Health and Sync Status

ArgoCD continuously monitors two critical dimensions of every application: health and sync status. These are separate but complementary indicators that tell you different things about your deployment.

Sync Status: Git vs Cluster Reality

Sync status answers: "Does what's running in my cluster match what's defined in Git?"

  • Synced: Kubernetes resources match the Git manifests exactly
  • OutOfSync: Differences detected between Git and cluster (manual changes, drift, or new commits)
  • Unknown: ArgoCD cannot determine status (connection issues, missing permissions)

Think of sync status like checking if your deployed code matches the committed version—it's about configuration alignment, not runtime behavior.

Health Status: Application Functionality

Health status answers: "Is my application actually working?"

  • Healthy: All resources are running as expected (Pods running, Deployments ready, Services available)
  • Progressing: Resources are being created or updated but not yet ready
  • Degraded: Some resources are failing (CrashLoopBackOff, failed readiness probes)
  • Suspended: Application intentionally paused or scaled to zero
  • Missing: Expected resources don't exist in the cluster

ArgoCD uses built-in health checks for standard Kubernetes resources (Deployments, StatefulSets, etc.) and can be extended with custom health checks for CRDs.

Why Both Matter

You might be Synced but Degraded (Git matches, but Pods crash). Or Healthy but OutOfSync (app runs fine, but someone made manual changes). Both views are essential for GitOps visibility.

Key Takeaway: ArgoCD's health status monitors runtime application state, while sync status ensures cluster configuration matches Git—together they provide complete visibility into your GitOps deployments.