Available on crate feature
deployment only.Expand description
ArgoCD sync-wave constants.
Convention for the order in which ArgoCD applies resources during a
sync. Lower waves run first. Used as the argocd.argoproj.io/sync-wave
annotation on Application resources and as the default for
crate::deployment::ArgocdConfig::sync_wave.
The numeric values are gaps wide enough that consumer projects can
slot custom waves (e.g. -15 for “between operators and CRDs”, -3
for “before topics but after CRDs”). Stick to the canonical bands
where possible – operators install order is genuinely
dependency-driven.
Constants§
- WAVE_
APPS - DFE apps themselves (loader, receiver, archiver, …). The default for any Application without an explicit sync wave.
- WAVE_
CRDS - Custom Resource Definitions that other resources depend on. Runs after operators (which often install their own CRDs).
- WAVE_
OPERATORS - Operators that must install before everything else (e.g. Strimzi Kafka Operator, External Secrets Operator). Their CRDs are prerequisites for later waves.
- WAVE_
POST - Post-deployment work: smoke tests, notification webhooks, observability registrations.
- WAVE_
TOPICS - Cross-application Kafka topology:
KafkaTopic,KafkaUser, and similar CRs that DFE apps consume.