Trying to add backups to existing cluster, `/run/etc/wal-e.d/env` is missing

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.11.0
• Where do you run it? GKE
• Are you running Postgres Operator in production? yes
• Type of issue? question

I'm trying to add backups to an existing cluster, to push WAL-E to GCS.

I first updated the Helm Chart as follows (after doing the GCP IAM stuff)

helm upgrade --install \
  postgres \
  postgres-operator-charts/postgres-operator \
  --reuse-values \
  --set aws_or_gcp.wal_gs_bucket=<bucket-name> \
  --set podServiceAccount.name=postgres-pod-custom \
  --namespace=operators \
  --wait

Was hoping that setting aws_or_gcp.wal_gs_bucket would be sufficient

I've also tried adding a ConfigMap for the operator

Still, the /run/etc/... directory that should house the necessary wal-e.d stuff does not exist

root@psql-0:/home/postgres# ls -lh
total 8.0K
lrwxrwxrwx 1 root     root    8 Mar  6 13:19 etc -> /run/etc    <- DOES NOT EXIST
drwxr-xr-x 4 root     root 4.0K Mar 22 23:55 pgdata
-rw-rw-r-- 1 postgres root  156 Mar  6 13:08 pgq_ticker.ini
lrwxrwxrwx 1 root     root   17 Mar  6 13:19 postgres.yml -> /run/postgres.yml

Any help & guidance is much appreciated, thanks!

Start with the Helm values for aws_or_gcp.wal_gs_bucket and podServiceAccount.name, then inspect the existing cluster pod and its ConfigMap or mounted configuration for the /run/etc/wal-e.d/env path. Confirm whether the upgraded operator propagated the backup settings to the existing cluster. Done means the WAL-E environment path exists and the cluster can use the configured GCS backup.