fix: Separate Backup CRs into their own kustomization

The Backup and Restore CRs need the rancher-backup CRDs to exist first.
Moved them to a separate kustomization that depends on the operator being ready.

infrastructure/addons/kustomization-rancher-backup-config.yaml

@@ -0,0 +1,16 @@
+apiVersion: kustomize.toolkit.fluxcd.io/v1
+kind: Kustomization
+metadata:
+  name: addon-rancher-backup-config
+  namespace: flux-system
+spec:
+  interval: 10m
+  prune: true
+  sourceRef:
+    kind: GitRepository
+    name: platform
+  path: ./infrastructure/addons/rancher-backup-config
+  timeout: 5m
+  suspend: false
+  dependsOn:
+    - name: addon-rancher-backup

infrastructure/addons/kustomization.yaml

@@ -13,3 +13,4 @@ resources:
   - kustomization-rancher.yaml
   - kustomization-rancher-config.yaml
   - kustomization-rancher-backup.yaml
+  - kustomization-rancher-backup-config.yaml

infrastructure/addons/rancher-backup-config/kustomization.yaml

@@ -0,0 +1,5 @@
+apiVersion: kustomize.config.k8s.io/v1beta1
+kind: Kustomization
+resources:
+  - backup-recurring.yaml
+  - restore-from-b2.yaml

infrastructure/addons/rancher-backup/kustomization.yaml

@@ -5,5 +5,3 @@ resources:
   - helmrepository-rancher-backup.yaml
   - helmrelease-rancher-backup.yaml
   - b2-credentials-externalsecret.yaml
-  - backup-recurring.yaml
-  - restore-from-b2.yaml

infrastructure/addons/rancher/rancher-tailscale-service.yaml

@@ -16,7 +16,3 @@ spec:
       port: 80
       protocol: TCP
       targetPort: 80
-    - name: https
-      port: 443
-      protocol: TCP
-      targetPort: 443