Argo CD does not have one universal pause switch. To stop automatic deployments while keeping an Application processed and its status current, disable automated sync. To stop reconciliation itself, use the experimental alpha skip-reconcile annotation instead. For teardown, PreDelete runs only when the whole Application is deleted—not when an ordinary sync prunes a resource.
Choose what “pause” means before changing Argo CD
There are three different ways to hold back changes, and they affect different parts of Argo CD. The distinction matters: an Application can remain actively processed even when automated deployments are disabled, while skipping reconciliation also stops status updates.
As an Amazon Associate I earn from qualifying purchases.
| Control | What it pauses | What continues |
|---|---|---|
| Automated sync disabled | Automatic application of desired-state changes | Application processing and status updates |
argocd.argoproj.io/skip-reconcile: "true" on an Application |
Application processing | Status is not updated while skipped; removing the annotation or setting it to false resumes processing |
| Sync window | Sync operations according to an allow or deny schedule | Reconciliation; manual override may be available depending on configuration |
These controls are described in the Argo CD automated sync and reconciliation documentation. The skip-reconcile annotation is documented as experimental alpha, introduced in v2.7.0; it is not the default choice for simply stopping automatic deployments.
Recommended Free Tools
Stop automatic deployments without stopping reconciliation
Set spec.syncPolicy.automated.enabled to false on the Application. Argo CD then skips automated sync, even if automated-sync options such as pruning or self-healing remain configured. This is the appropriate control when you want Argo CD to keep processing the Application without automatically applying changes.
#1 Best Overall
spec:
syncPolicy:
automated:
enabled: false
prune: true
selfHeal: trueThe example preserves the other automated-sync settings to illustrate that they do not override enabled: false. It does not disable manual syncs or suspend Application processing; use a sync window if you need a scheduled sync gate.
When to suspend reconciliation instead
Annotate an Application with argocd.argoproj.io/skip-reconcile: "true" when you need its controller processing suspended, not merely automatic deployments blocked. While skipped, the Application status is not updated. Remove the annotation or change its value to false to resume processing.
There is also a cluster-level form: putting argocd.argoproj.io/skip-reconcile: "true" on the Argo CD cluster Secret prevents the Application controller from reconciling all Applications targeting that cluster. The cluster remains visible in API responses but is treated as unmanaged; removing the annotation resumes reconciliation. This is broader than pausing one Application, so use it only when the intended scope is every app targeting that cluster.
For ApplicationSet apps, change the owning template
If an Application is generated by an ApplicationSet, make the automated-sync policy change in the ApplicationSet template. Editing the generated Application directly is not a durable control point: the ApplicationSet reconciles it back to the template’s state. The same ownership principle applies when choosing the intended policy for generated apps; manage it where it is declared.
What PreDelete does—and when it runs
PreDelete is a hook phase for work that must happen before the resources belonging to an entire Application are deleted. The Argo CD documentation states, “PreDelete hooks execute before an Application and its resources are deleted.” The controller creates and runs the hook, waits for it to become Healthy, and then proceeds with deleting the Application resources.
PreDelete does not run for ordinary sync pruning, even when pruning is enabled. Pruning deletes resources removed from desired state during a sync; it is not deletion of the Application itself. Hooks also do not run during selective sync operations. See the Argo CD Sync Phases and Waves documentation.
Rank #3
Use PreDelete for whole-Application prerequisites
A teardown hook might, for example, export state or remove an external dependency before the Application’s Kubernetes resources disappear. Treat that as a design pattern, not a guarantee that an external operation will succeed: the hook must complete successfully enough for Argo CD to observe it as Healthy before deletion can continue.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallKnow how to recover a blocked deletion
A failing PreDelete Job or Pod can block Application deletion. The Application may remain in a deleting state with a DeletionError. The documented recovery options are to fix the hook manifest in Git so reconciliation can retry, or manually delete the failing hook resource. Choose based on whether the hook should be rerun and whether its failure cause has been addressed.
Use PostDelete for work after resources are gone
PostDelete runs after all Application resources have been removed, making it suitable for after-deletion cleanup or notifications. The Argo CD documentation says this phase is available starting in v2.10. If a PostDelete hook fails, the Application custom resource can remain with a DeletionError, even though its Application resources have already been deleted. That is a different recovery situation from a PreDelete failure: the main resource teardown has already happened.
Order resource operations with sync waves
Use the argocd.argoproj.io/sync-wave annotation to assign an integer wave to a resource. Lower-numbered waves apply first; the default is wave zero. During pruning, the order reverses, so higher-numbered waves are removed first. Within that ordering, Argo CD sorts by phase, wave, kind, then name.
This lets teams express dependencies in a manifest set—for example, applying a prerequisite before a dependent resource and removing the dependent resource first. A pruning failure in one wave can fail the operation and stop processing lower waves, so a wave number is an ordering mechanism, not a guarantee that every later deletion will proceed after an error.
Keep hook cleanup under Argo CD’s control
Hooks are Kubernetes resources marked with argocd.argoproj.io/hook; Jobs and Workflows are common choices. For Jobs, prefer Argo CD’s hook deletion policies over Kubernetes’ ttlSecondsAfterFinished when Argo CD needs to read the Job’s result. If Kubernetes removes a finished Job before Argo CD reads its phase, the sync may wait on a hook that no longer exists.
| Hook delete policy | Effect |
|---|---|
HookSucceeded |
Delete the hook after it succeeds |
HookFailed |
Delete the hook after it fails |
BeforeHookCreation |
Delete an existing hook before creating a new instance |
Choose a policy that fits how operators need to inspect or retry the hook. These policies and the warning about TTL cleanup are documented in Sync Phases and Waves.
What these controls imply for Kubernetes deployments
The practical direction is to treat deployment gating, reconciliation suspension, and teardown orchestration as separate design decisions. Use automated-sync policy when the desired state should still be observed but not automatically applied; use skip-reconcile only when processing itself must stop and its alpha status is acceptable; use sync windows for schedule-based gates. For deletion, distinguish pruning from deleting an Application, put whole-Application prerequisites in PreDelete, post-removal work in PostDelete, and encode resource dependencies with waves.
These are implications of current documented capabilities, not a forecast of an Argo CD roadmap or a claim about industry adoption. Teams should also account for ownership: where an ApplicationSet generates an Application, the template is the effective policy source.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
