Argo CD Sync Waves: Apply Order

Argo CD Sync Waves: Apply Order A workflow diagram generated by Archify. 01 / Argo CD sync (lowest sync-wave first) Negative waves Default wave Positive waves Wave -2 · CRDs · Argo CD sync (lowest sync-wave first) › Negative waves · 1 kind Wave -2 CRDs 1 kind Wave -1 · Namespaces, ServiceAccounts · Argo CD sync (lowest sync-wave first) › Negative waves · 2 kinds Wave -1 Namespaces, ServiceAccounts 2 kinds Wave 0 · ConfigMaps, Secrets, Deployments · Argo CD sync (lowest sync-wave first) › Default wave · default · 3 kinds Wave 0 ConfigMaps, Secrets, Deployments default · 3 kinds Wave 1 · Services, Ingress · Argo CD sync (lowest sync-wave first) › Positive waves · 2 kinds Wave 1 Services, Ingress 2 kinds healthy healthy healthy

How Waves Work

  • • Lowest wave number first (can be negative)
  • • Within a wave, hooks run first, then resources
  • • Next wave starts only after the previous one completes

Setting the Wave

  • • Annotation: argocd.argoproj.io/sync-wave: "-2"
  • • Resources without the annotation default to wave 0
  • • Argo CD waits for the previous wave's resources to become healthy before continuing