fix(cloudnative-pg): fix barman backups retention policy

prehor · Jan 31, 2025 · 3e357d9 · 3e357d9
1 parent 5b299bd
commit 3e357d9
Showing 1 changed file with 4 additions and 4 deletions.
diff --git a/kubernetes/main/apps/database/cloudnative-pg/cluster/postgres17.yaml b/kubernetes/main/apps/database/cloudnative-pg/cluster/postgres17.yaml
@@ -42,8 +42,10 @@ spec:
       - { sourceLabels: ["cluster"], targetLabel: cnpg_cluster, action: replace }
       - { regex: cluster, action: labeldrop }
   backup:
-    retentionPolicy: 30d
     barmanObjectStore: &barmanObjectStore
+      # Note: serverName version needs to be incremented
+      # when recovering from an existing cnpg cluster
+      serverName: &currentCluster postgres17-v1
       data:
         compression: bzip2
         encryption: AES256
@@ -52,16 +54,14 @@ spec:
         encryption: AES256
       destinationPath: s3://home-ops-postgresql
       endpointURL: https://s3.${STORAGE_DOMAIN}
-      # Note: serverName version needs to be incremented
-      # when recovering from an existing cnpg cluster
-      serverName: &currentCluster postgres17-v1
       s3Credentials:
         accessKeyId:
           name: postgres-cluster-secret
           key: MINIO_ACCESS_KEY
         secretAccessKey:
           name: postgres-cluster-secret
           key: MINIO_SECRET_KEY
+    retentionPolicy: "30d"
   bootstrap:
     ### Initialize new cluster
     initdb: