Annotate UpgradeJobHook to avoid blocking initial sync

Depending on bootstrap order, this component may try to sync itself
before the upgrade controller custom resources are available. To allow a
partial sync to succeed in that case, we annotate the `UpgradeJobHook`
resource with ArgoCD sync option `SkipDryRunOnMissingResource=true`.

Author: simu

component/notifications.libsonnet

@@ -193,6 +193,11 @@ local hookScript = kube.ConfigMap('cleanup-upgrade-notification') + upgradeContr
 };
 
 local ujh = kube._Object('managedupgrade.appuio.io/v1beta1', 'UpgradeJobHook', 'cleanup-upgrade-notification') + upgradeControllerNS {
+  metadata+: {
+    annotations+: {
+      'argocd.argoproj.io/sync-options': 'SkipDryRunOnMissingResource=true',
+    },
+  },
   spec+: {
     selector: {
       matchLabels: {

tests/golden/upgrade-notification/openshift4-console/openshift4-console/31_upgrade_notification.yaml

@@ -144,7 +144,8 @@ metadata:
 apiVersion: managedupgrade.appuio.io/v1beta1
 kind: UpgradeJobHook
 metadata:
-  annotations: {}
+  annotations:
+    argocd.argoproj.io/sync-options: SkipDryRunOnMissingResource=true
   labels:
     name: cleanup-upgrade-notification
   name: cleanup-upgrade-notification