Sync waves#

MonitoringChart annotates every resource with an argocd.argoproj.io/sync-wave value. ArgoCD applies lower waves before higher waves, which gives the stack a deterministic rollout order. The waves run from 0 to 3.

Wave 0: foundation#

These resources must exist before anything references them.

Resource	Construct
`Namespace`	`NamespaceConstruct`
`PriorityClass` `high-priority`	`PriorityClassConstruct`

The PriorityClass exists only when priorityClasses.create is true.

Wave 1: external dependencies#

Buckets and credentials must exist before pods try to read storage or mount secrets.

Resource	Construct
Thanos S3 `Bucket` (Crossplane)	`ThanosS3BucketConstruct`
Loki S3 `Bucket` (Crossplane)	`LokiS3BucketConstruct`
Thanos S3 `ExternalSecret`	`ThanosS3CredentialsConstruct`
Loki S3 `ExternalSecret`	`LokiS3CredentialsConstruct`
Grafana admin `ExternalSecret`	`GrafanaPasswordSecret`

Wave 2: core services#

The core stack starts once its storage and secrets are in place.

Resource	Construct
kube-prometheus-stack `HelmChart`	`PrometheusStackConstruct`
Loki `HelmChart`	`LokiConstruct`

Wave 3: advanced services#

Collection, querying, and long-term storage start after the core services.

Resource	Construct
Alloy `HelmChart`	`AlloyConstruct`
Thanos Query `Deployment` and `Service`s	`ThanosQueryConstruct`
Thanos Store `StatefulSet` and `Service`s	`ThanosStoreConstruct`
Thanos Compactor `StatefulSet` and `Service`	`ThanosCompactorConstruct`

Tracing resources#

These resources exist only when config.tempo.enabled is true. They occupy the same waves as their non-tracing counterparts: storage and credentials in wave 1, workloads in wave 3.

Resource	Construct	Wave
Tempo S3 `Bucket` (Crossplane)	`TempoS3BucketConstruct`	1
Tempo S3 `ExternalSecret`	`TempoS3CredentialsConstruct`	1
Tempo `HelmChart`	`TempoConstruct`	3
Alloy traces `HelmChart`	`AlloyTracesConstruct`	3

Infrastructure monitor resources#

These resources exist only when their block is enabled. They carry no sync-wave annotation, so ArgoCD applies them in wave 0.

Resource	Construct	Condition
`PodMonitor` `traefik-metrics`	`TraefikMonitorConstruct`	`traefik.enabled`
`ConfigMap` `traefik-dashboard`	`TraefikMonitorConstruct`	`traefik.enabled` and `traefik.dashboard`
`ServiceMonitor` `longhorn-metrics`	`LonghornMonitorConstruct`	`longhorn.enabled`
`PrometheusRule` `longhorn-volume-health`	`LonghornMonitorConstruct`	`longhorn.enabled` and `longhorn.alerts`

The PodMonitor, ServiceMonitor, and PrometheusRule kinds come from the prometheus-operator CRDs, which must exist before the first sync. See Set up prerequisites.

Application dashboards and alerts#

The library does not place application dashboards or alerts in any wave; it ships none. Integration charts attach their own dashboard and alert constructs and choose a wave for them. Wave 3 is a natural fit, since the dashboards are discovered after Grafana is running. See Add application dashboards and alerts.