Home / CI/CD / Fix ArgoCD Application Out of Sync (cicd variant 2)

CI/CD

Fix ArgoCD Application Out of Sync (cicd variant 2)

Resolve ArgoCD application out of sync errors by checking sync status, configuration drift, and automatic sync settings.

Published: Apr 11, 20267 min readBy FixWikiHub Editorial Team

Abstract illustration for a troubleshooting knowledge base category.

Introduction

ArgoCD applications show OutOfSync status. Git repository changes are not applied to cluster, live state differs from desired state, or automatic sync is not working.

Symptoms

Application status:

```bash argocd app list

NAME CLUSTER NAMESPACE STATUS HEALTH SYNCPOLICY my-app https://k8s... default OutOfSync Healthy Auto

argocd app get my-app --refresh

Name: my-app Project: default Server: https://kubernetes.default.svc Namespace: default URL: https://argocd/applications/my-app Repo: https://github.com/org/repo Target: HEAD Sync Status: OutOfSync from HEAD (abc123) Health Status: Healthy ```

Sync window:

bash

Sync Windows:  current:  enabled
               next:    2024-01-01 10:00:00 UTC

Common Causes

1.Config drift - Manual changes in cluster
2.Git changes - New commits not synced
3.Sync disabled - Automatic sync not enabled
4.Sync window - Sync blocked by sync window
5.Failed sync - Previous sync failed
6.Missing permissions - ArgoCD cannot apply resources
7.Helm/Kustomize issues - Template rendering errors

Step-by-Step Fix

1.Check logs for specific error messages
2.Verify configuration settings
3.Test network connectivity
4.Review recent changes
5.Apply corrective action
6.Verify the fix

Step 1: Check Application Sync Status

```bash argocd app list

argocd app get my-app

argocd app get my-app --refresh

argocd app diff my-app

argocd app diff my-app --local ./manifests

argocd app history my-app

argocd app manifests my-app ```

Step 2: Check Sync Policy

```bash argocd app get my-app | grep -A 5 "Sync Policy"

# Enable auto sync: argocd app set my-app --sync-policy automated

# Enable auto prune: argocd app set my-app --auto-prune

# Enable self heal: argocd app set my-app --self-heal

# Disable auto sync: argocd app set my-app --sync-policy none

# Check app YAML: kubectl get application my-app -n argocd -o yaml | grep -A 10 syncPolicy ```

Step 3: Check for Configuration Drift

```bash argocd app diff my-app

# Diff shows differences between Git and live

# Detailed diff: argocd app diff my-app --revision HEAD

# View resources with drift: argocd app resources my-app

# Check specific resource: kubectl get deployment my-deployment -o yaml

# Compare with Git: git show HEAD:k8s/deployment.yaml ```

Step 4: Manual Sync Application

```bash # Sync application: argocd app sync my-app

# Sync specific resources: argocd app sync my-app --resource deployment:my-deployment

# Sync with prune: argocd app sync my-app --prune

# Sync with replace: argocd app sync my-app --replace

# Sync to specific revision: argocd app sync my-app --revision abc123

# Dry run sync: argocd app sync my-app --dry-run

# Force sync: argocd app sync my-app --force ```

Step 5: Check Sync Windows

```bash # Sync windows block syncing during certain times

argocd app get my-app | grep -A 5 "Sync Windows"

# Check project sync windows: argocd proj get default | grep -A 10 "Sync Windows"

# View application sync windows: kubectl get application my-app -n argocd -o jsonpath='{.spec.syncPolicy.syncWindows}'

# View project sync windows: kubectl get appproject default -n argocd -o jsonpath='{.spec.syncWindows}'

# Skip sync window for manual sync: argocd app sync my-app --async ```

Step 6: Check Repository Access

```bash # ArgoCD must access Git repository

argocd repo list

argocd repo get https://github.com/org/repo

# Test repo access: argocd repo get https://github.com/org/repo --type git

# Check repo credentials: kubectl get secret -n argocd | grep repo

# Add repo if missing: argocd repo add https://github.com/org/repo --username user --password token

# Check SSH key: kubectl get secret -n argocd argocd-ssh-key -o jsonpath='{.data.sshPrivateKey}' ```

Step 7: Check Application Controller

```bash # ArgoCD application controller manages sync

kubectl get pods -n argocd -l app.kubernetes.io/name=argocd-application-controller

kubectl logs -n argocd -l app.kubernetes.io/name=argocd-application-controller

kubectl describe pod -n argocd -l app.kubernetes.io/name=argocd-application-controller

# Check controller status: kubectl get applicationcontroller -n argocd

# Check controller metrics: kubectl port-forward -n argocd svc/argocd-metrics 8082:8082 & curl localhost:8082/metrics | grep argocd ```

Step 8: Check Resource Permissions

```bash # ArgoCD needs permissions to manage resources

# Check ArgoCD RBAC: kubectl get clusterrole argocd-application-controller -o yaml

kubectl get clusterrolebinding argocd-application-controller -o yaml

# Check service account: kubectl get serviceaccount -n argocd argocd-application-controller

# Test permissions: kubectl auth can-i create deployments --as=system:serviceaccount:argocd:argocd-application-controller -n default

# Check for permission errors: kubectl logs -n argocd -l app.kubernetes.io/name=argocd-application-controller | grep -i "forbidden|unauthorized" ```

Step 9: Check Helm and Kustomize Issues

```bash # For Helm applications:

argocd app get my-app --helm-set image.tag=v2.0.0

argocd app get my-app --helm-values values.yaml

# Check Helm version: argocd version | grep Helm

# Check Helm values: kubectl get application my-app -n argocd -o jsonpath='{.spec.source.helm}'

# For Kustomize:

argocd app get my-app --kustomize-image myimage:v2.0.0

# Check Kustomize version: argocd version | grep Kustomize

# Check Kustomize overlays: kubectl get application my-app -n argocd -o jsonpath='{.spec.source.kustomize}' ```

Step 10: Monitor ArgoCD Applications

```bash # Monitor application status: watch -n 10 argocd app list

# Monitor sync status: watch -n 10 'argocd app list | grep OutOfSync'

# Check application events: kubectl get events -n argocd --field-selector involvedObject.name=my-app

# ArgoCD UI: # https://argocd/applications

# Prometheus metrics: kubectl port-forward -n argocd svc/argocd-metrics 8082:8082 & curl localhost:8082/metrics | grep argocd_application ```

ArgoCD Application OutOfSync Checklist

Check	Command	Expected
App status	argocd app get	Synced
Sync policy	argocd app get	Auto sync enabled
Diff	argocd app diff	No differences
Repo access	argocd repo get	Connected
Permissions	kubectl auth can-i	Allowed
Controller	kubectl get pods	Running

Verification

```bash # 1. Check application synced argocd app get my-app | grep "Sync Status" // Synced

# 2. Check no diff argocd app diff my-app // No differences

# 3. Check health argocd app get my-app | grep "Health Status" // Healthy

# 4. Check resources match kubectl get all -n default // Resources match Git

# 5. Monitor stability watch -n 30 argocd app get my-app // Stays Synced

# 6. Check logs kubectl logs -n argocd -l app.kubernetes.io/name=argocd-application-controller --since 5m | grep -i error // No errors ```

[Fix ArgoCD Application Degraded](/articles/fix-argocd-application-degraded)
[Fix ArgoCD Sync Failed](/articles/fix-argocd-sync-failed)
[Fix GitLab CI Pipeline Stuck](/articles/fix-gitlab-ci-pipeline-stuck)

[Technical troubleshooting: Fix Cicd Artifact Upload Failed Storage Issue in C](cicd-artifact-upload-failed-storage)
[Technical troubleshooting: Fix Cicd Code Quality Gate Failed Sonarqube Issue ](cicd-code-quality-gate-failed-sonarqube)
[Technical troubleshooting: Fix Cicd Deployment Failed Health Check Issue in C](cicd-deployment-failed-health-check)
[Technical troubleshooting: Fix Cicd Github Actions Workflow Queue Timeout in ](cicd-github-actions-workflow-queue-timeout)
[Technical troubleshooting: Fix Cicd Gitlab Runner Stuck Pending Issue in CI/C](cicd-gitlab-runner-stuck-pending)

Was this guide helpful?

Related search paths

People also search for

If the symptom is close but not identical, these search paths usually surface the right neighboring fixes faster than scrolling the full archive.

ArgoCD Application Out of Sync (cicd variant 2)ArgoCD Application Out of Sync (cicd variant 2) CI/CD ArgoCD Application Out of Sync (cicd variant 2) troubleshooting ArgoCD Application Out of Sync (cicd variant 2) fix Resolve ArgoCD application out of sync errors by checking sync status, configuration drift, and automatic sync settings CI/CD Resolve ArgoCD application out of sync errors by checking sync status, configuration drift, and automatic sync settings

Explore Related Topics

Browse Guides from Other Categories

Discover troubleshooting guides from related categories to expand your knowledge.

FAQ

CI/CD Troubleshooting FAQs

Common questions about troubleshooting and preventing similar issues

How do I know if this cicd-errors troubleshooting guide applies to my situation?

This guide is designed for cicd-errors issues. If you're experiencing similar symptoms described in the article, follow the step-by-step instructions. Start with the most common causes and work through the diagnostic process.

Is it safe to follow these cicd-errors troubleshooting steps?

Yes, all steps are designed to be safe and non-destructive. We recommend creating backups before making significant changes and testing each step before proceeding to the next.

How long does it typically take to resolve this type of cicd-errors issue?

Most cicd-errors issues can be resolved within 30 minutes to 2 hours, depending on the complexity and root cause. Follow the troubleshooting flow to identify and fix the problem efficiently.

How can I prevent this cicd-errors issue from happening again?

Regular maintenance, monitoring, and following best practices for cicd-errors configuration can help prevent recurrence. Consider implementing automated checks and alerts for early detection.

Written by

FixWikiHub Editorial Team

Our editorial team consists of experienced DevOps engineers, systems administrators, and cloud architects with hands-on experience in production environments across AWS, Azure, GCP, and on-premises infrastructure.

Every guide undergoes technical review for accuracy and is updated when software versions, commands, or best practices change.

Last updated: Apr 11, 2026

About our team

Important Notice

Disclaimer & Safety Guidelines

The troubleshooting steps in this guide are provided for educational and informational purposes. Before applying any changes to production systems:

Test in a staging environment first — Always verify commands and configurations in a non-production environment before deploying to live systems.
Create backups — Ensure you have current backups of databases, configurations, and critical files before making changes.
Understand the impact — Review how each step may affect your specific environment, dependencies, and users.
Consult official documentation — This guide supplements, but does not replace, official vendor documentation and best practices.

FixWikiHub is not responsible for any damages arising from the use of this content. See our Terms of Use for more information.

Resources

Official Documentation & Further Reading

For authoritative information, consult the official documentation for the technologies discussed in this guide. Our troubleshooting content supplements, but does not replace, vendor documentation.

AWS Documentation — Official Amazon Web Services guides and API references
Kubernetes Documentation — Official Kubernetes documentation
Nginx Documentation — Official Nginx web server documentation
Apache Documentation — Official Apache HTTP Server documentation
Docker Documentation — Official Docker container documentation

Fix ArgoCD Application Out of Sync (cicd variant 2)

Introduction

Symptoms

Common Causes

Step-by-Step Fix

Step 1: Check Application Sync Status

Step 2: Check Sync Policy

Step 3: Check for Configuration Drift

Step 4: Manual Sync Application

Step 5: Check Sync Windows

Step 6: Check Repository Access

Step 7: Check Application Controller

Step 8: Check Resource Permissions

Step 9: Check Helm and Kustomize Issues

Step 10: Monitor ArgoCD Applications

ArgoCD Application OutOfSync Checklist

Verification

People also search for

Browse Guides from Other Categories

WordPress

SSL

DNS

CI/CD Troubleshooting FAQs

FixWikiHub Editorial Team

Disclaimer & Safety Guidelines

Official Documentation & Further Reading

Fix ArgoCD Application Out of Sync (cicd variant 2)

Introduction

Symptoms

Common Causes

Step-by-Step Fix

Step 1: Check Application Sync Status

Step 2: Check Sync Policy

Step 3: Check for Configuration Drift

Step 4: Manual Sync Application

Step 5: Check Sync Windows

Step 6: Check Repository Access

Step 7: Check Application Controller

Step 8: Check Resource Permissions

Step 9: Check Helm and Kustomize Issues

Step 10: Monitor ArgoCD Applications

ArgoCD Application OutOfSync Checklist

Verification

Related Issues

Related Articles

People also search for

Share this guide

More CI/CD Troubleshooting Guides

Browse Guides from Other Categories

CI/CD Troubleshooting FAQs

FixWikiHub Editorial Team

Disclaimer & Safety Guidelines

Official Documentation & Further Reading