Please, answer some short questions which should help us to understand your problem / question better?
Which image of the operator are you using? registry.opensource.zalan.do/acid/postgres-operator:v1.9.0
Where do you run it - cloud or metal? Kubernetes or OpenShift? GKE
Are you running Postgres Operator in production? yes
Type of issue? Question
The Postgres Operator documentation lists two ways to configure GCS access for WAL backups. However, both are global configurations at the operator level.
Is there a way to configure the WALG_GS_PREFIX (and possibly the service account or key.json) at postgres cluster level?
We previously backed up to MinIO using the Postgres S3 config. Here, I was able to set the bucket at cluster level by defining the WAL_S3_BUCKET env variable. Similarly setting WALG_GS_PREFIX in the postgres resource does not seem to work.
Please, answer some short questions which should help us to understand your problem / question better?
The Postgres Operator documentation lists two ways to configure GCS access for WAL backups. However, both are global configurations at the operator level.
Is there a way to configure the
WALG_GS_PREFIX(and possibly the service account or key.json) at postgres cluster level?We previously backed up to MinIO using the Postgres S3 config. Here, I was able to set the bucket at cluster level by defining the
WAL_S3_BUCKETenv variable. Similarly settingWALG_GS_PREFIXin the postgres resource does not seem to work.