ArgoCD 3.3 PreDelete Hook — Making GitOps Deletion a Safe Lifecycle
Why ArgoCD 3.3 Deserves Your Attention On February 28, 2026, ArgoCD 3.3 was released. Rather than major architectural changes, this release focused on filling long-needed gaps in production operati...
Source: DEV Community
Why ArgoCD 3.3 Deserves Your Attention On February 28, 2026, ArgoCD 3.3 was released. Rather than major architectural changes, this release focused on filling long-needed gaps in production operations. The most significant change is the introduction of the PreDelete Hook. In GitOps workflows, deletion has always been a risky operation. When stateful applications are abruptly removed, data can be lost or dependent external systems lose service without notification. ArgoCD 3.3 elevates deletion to an explicit lifecycle stage. PreDelete Hook: Deletion as a Lifecycle Stage Traditional ArgoCD provided three hook stages: PreSync → Sync → PostSync. With PreDelete added in 3.3, the complete application lifecycle is now realized. When a deletion request arrives, the PreDelete Hook executes a designated Kubernetes Job before actual resource removal. Deletion proceeds only if this Job succeeds; failure blocks deletion entirely. # PreDelete Hook example: Database backup before deletion apiVersion:
