chore: Update manifests after change

clusters/cl01tl/manifests/komodo/Cluster-komodo-postgresql-17-fdb-cluster.yaml

@@ -68,15 +68,11 @@ spec:
         barmanObjectName: "komodo-postgresql-17-fdb-backup-garage-local"
         serverName: "komodo-postgresql-17-fdb-backup-2"
   bootstrap:
-    recovery:
+    initdb:
-      database: app
+      database: ferretDB
-      source: komodo-postgresql-17-fdb-backup-1
+      owner: ferret
+      postInitApplicationSQL:
+        - create extension if not exists pg_cron;
+        - create extension if not exists documentdb cascade;
+        - grant documentdb_admin_role to ferret;
   externalClusters:
-    - name: komodo-postgresql-17-fdb-backup-1
-      plugin:
-        name: barman-cloud.cloudnative-pg.io
-        enabled: true
-        isWALArchiver: false
-        parameters:
-          barmanObjectName: "komodo-postgresql-17-fdb-recovery"
-          serverName: komodo-postgresql-17-fdb-backup-1

clusters/cl01tl/manifests/komodo/ScheduledBackup-komodo-postgresql-17-fdb-scheduled-backup-live-backup.yaml

@@ -13,7 +13,7 @@ metadata:
     app.kubernetes.io/name: "komodo-postgresql-17-fdb-scheduled-backup-live-backup"
 spec:
   immediate: true
-  suspend: true
+  suspend: false
   schedule: "0 0 0 * * *"
   backupOwnerReference: self
   cluster: