Understanding Argo CD Pods: Which One to Restart (and Why) When Argo CD behaves unexpectedly — sync stuck, UI showing wrong state, or deployments failing — the key is knowing which Argo CD pod actually does what . Restarting the wrong pod wastes time. Restarting the right one fixes the issue in minutes. Argo CD Core Pods Overview Run this command to see all Argo CD pods: kubectl -n argocd get pods You’ll typically see: argocd-application-controller-0 argocd-server argocd-repo-server argocd-dex-server 1. argocd-application-controller (The Most Important Pod) This is the brain and worker of Argo CD. What it does Compares Git state vs cluster state Executes syncs and deployments Applies manifests to Kubernetes Runs hooks and manages rollouts Updates application health and sync status Symptoms when it is broken Sync stuck or terminating another operation is already in progress Apps appear healthy but cannot deploy...