fix: deploy monitoring and pihole after tailscale

When destroying, this stops the external service from deleting
mrsimonemms · Dec 12, 2024 · c1f926e · c1f926e
1 parent f4ba970
commit c1f926e
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 3 deletions.
diff --git a/registry/clusters/dev/components/monitoring.yaml b/registry/clusters/dev/components/monitoring.yaml
@@ -4,7 +4,7 @@ metadata:
   name: monitoring-components
   namespace: argocd
   annotations:
-    argocd.argoproj.io/sync-wave: "10"
+    argocd.argoproj.io/sync-wave: "20"
   finalizers:
     - resources-finalizer.argocd.argoproj.io
 spec:

diff --git a/registry/clusters/prod/components/monitoring.yaml b/registry/clusters/prod/components/monitoring.yaml
@@ -4,7 +4,7 @@ metadata:
   name: monitoring-components
   namespace: argocd
   annotations:
-    argocd.argoproj.io/sync-wave: "10"
+    argocd.argoproj.io/sync-wave: "20"
   finalizers:
     - resources-finalizer.argocd.argoproj.io
 spec:

diff --git a/registry/clusters/prod/components/pihole-ingress.yaml b/registry/clusters/prod/components/pihole-ingress.yaml
@@ -4,7 +4,7 @@ metadata:
   name: pihole-ingress-components
   namespace: argocd
   annotations:
-    argocd.argoproj.io/sync-wave: "10"
+    argocd.argoproj.io/sync-wave: "20"
   finalizers:
     - resources-finalizer.argocd.argoproj.io
 spec: