chore: Update manifests after change

This commit is contained in:
2025-12-12 23:33:09 +00:00
parent 7a1a7336f6
commit 8c9b7be4f3
2 changed files with 47 additions and 21 deletions

View File

@@ -29,6 +29,13 @@ spec:
parameters:
barmanObjectName: "lidarr-postgresql-18-garage-local-backup"
serverName: "lidarr-postgresql-18-backup-1"
externalClusters:
- name: recovery
plugin:
name: barman-cloud.cloudnative-pg.io
parameters:
barmanObjectName: "lidarr-postgresql-18-recovery"
serverName: lidarr-postgresql-18-backup-1
storage:
size: 10Gi
storageClass: local-path
@@ -58,25 +65,15 @@ spec:
enablePodMonitor: true
disableDefaultQueries: false
bootstrap:
initdb:
import:
source:
externalCluster: importSource
type: monolith
databases:
- lidarr-main
- lidarr-log
roles:
- app
schemaOnly: false
recovery:
database: app
source: lidarr-postgresql-18-backup-1
externalClusters:
- name: importSource
connectionParameters:
host: "lidarr2-postgresql-17-cluster-rw"
port: "5432"
user: "postgres"
dbname: "*"
sslmode: "disable"
password:
name: lidarr2-postgresql-17-cluster-superuser
key: password
- name: lidarr-postgresql-18-backup-1
plugin:
name: barman-cloud.cloudnative-pg.io
enabled: true
isWALArchiver: false
parameters:
barmanObjectName: "lidarr-postgresql-18-recovery"
serverName: lidarr-postgresql-18-backup-1

View File

@@ -0,0 +1,29 @@
apiVersion: barmancloud.cnpg.io/v1
kind: ObjectStore
metadata:
name: "lidarr-postgresql-18-recovery"
namespace: lidarr
labels:
helm.sh/chart: postgres-18-cluster-6.17.1
app.kubernetes.io/name: lidarr-postgresql-18
app.kubernetes.io/instance: lidarr
app.kubernetes.io/part-of: lidarr
app.kubernetes.io/version: "6.17.1"
app.kubernetes.io/managed-by: Helm
spec:
configuration:
destinationPath: s3://postgres-backups/cl01tl/lidarr/lidarr-postgresql-18-cluster
endpointURL: http://garage-main.garage:3900
wal:
compression: snappy
maxParallel: 1
data:
compression: snappy
jobs: 1
s3Credentials:
accessKeyId:
name: lidarr-postgresql-18-cluster-backup-secret
key: ACCESS_KEY_ID
secretAccessKey:
name: lidarr-postgresql-18-cluster-backup-secret
key: ACCESS_SECRET_KEY