- Notifications
You must be signed in to change notification settings - Fork6.3k
Description
I have a production database that I want to periodically sync to our testing server for troubleshooting. I've been able to do this by setting up repo and a datasource. However, I obviously don't want this testing database to sync back to the same repo. So in order to do this I set the schedule to null and used read only credentials:
apiVersion: postgres-operator.crunchydata.com/v1beta1kind: PostgresClustermetadata: name: mytestingdatabasespec: dataSource: postgresCluster: clusterName: mydatabase repoName: repo2 postgresVersion: 16 instances: - name: mydatabase1 replicas: 1 dataVolumeClaimSpec: accessModes: - "ReadWriteOnce" resources: requests: storage: 10Gi users: - name: mydatabase databases: - mydatabase password: type: AlphaNumeric backups: pgbackrest: global: repo2-path: /pgbackrest/postgres-operator/mydatabase/repo2 repo2-retention-full: "7" repo2-retention-full-type: time configuration: - secret: name: pgo-s3-readonlycredentials repos: - name: repo2 schedules: null s3: bucket: "mydatabase-backups-pgo" endpoint: "someuuid.eu.r2.cloudflarestorage.com" region: "auto"proxy: pgBouncer: config: global: pool_mode: transaction ignore_startup_parameters: search_path,extra_float_digits replicas: 2 affinity: podAntiAffinity: preferredDuringSchedulingIgnoredDuringExecution: - weight: 1 podAffinityTerm: topologyKey: kubernetes.io/hostname labelSelector: matchLabels: postgres-operator.crunchydata.com/cluster: mydatabase postgres-operator.crunchydata.com/role: pgbouncermonitoring: pgmonitor: exporter: {}However, a job is still being started periodically calledmytestingdatabase-backup-t9f4 (ofc. with different t9f4 each time) attempting (and failing) sync wall segments.
I've also tried setting deletingschedules entirely and settingfull,incremental anddifferential tonull, but none of them had the desired effect of keeping the job from being created. So how do I properly disable back-ups?
To be clear I don't see anycronjobs being created, but ajob is still coming from 'somewhere'.