Fix initial sync for ClusterLogForwarder resources

Add `SkipDryRunOnMissingResource=true` to `ClusterLogForwarder` so that the initial sync of the openshift4-logging ArgoCD app can succeed.
appuio · Nov 19, 2024 · 867b9dc · 867b9dc
1 parent 85f5517
commit 867b9dc
Showing 1 changed file with 10 additions and 0 deletions.
diff --git a/component/config_forwarding.libsonnet b/component/config_forwarding.libsonnet
@@ -225,6 +225,11 @@ local unfoldSpecs(specs) = {
 // ClusterLogForwarder:
 // Create definitive ClusterLogForwarder resource from specs.
 local clusterLogForwarder = lib.ClusterLogForwarder(params.namespace, 'instance') {
+  metadata+: {
+    annotations+: {
+      'argocd.argoproj.io/sync-options': 'SkipDryRunOnMissingResource=true',
+    },
+  },
   spec: unfoldSpecs(clusterLogForwarderSpec),
 };
 
@@ -243,6 +248,11 @@ local namespaceLogForwarder = [
   local serviceAccount = std.get(specs, 'serviceAccountName', utils.namespacedName(forwarder).name);
 
   lib.ClusterLogForwarder(namespace, name) {
+    metadata+: {
+      annotations+: {
+        'argocd.argoproj.io/sync-options': 'SkipDryRunOnMissingResource=true',
+      },
+    },
     spec: { serviceAccountName: serviceAccount } + com.makeMergeable(unfoldSpecs(specs)),
   }
   for forwarder in std.objectFields(params.namespaceLogForwarder)