Which image of the operator are you using? e.g. registry.opensource.zalan.do/acid/postgres-operator:v1.8.2
registry.opensource.zalan.do/acid/postgres-operator:v1.8.2
Where do you run it - cloud or metal? Kubernetes or OpenShift? [AWS K8s | GCP ... | Bare Metal K8s]
It runs in the cloud (Digital Ocean)
Are you running Postgres Operator in production? [yes | no]
Not yet
Type of issue? [Bug report, question, feature request, etc.]
Question ~ Bug
I'm trying to set up the AWS S3 backup. To do so, I have used the ConfigMap from this URL -> https://github.com/zalando/postgres-operator/blob/master/manifests/configmap.yaml. It seems the operator doesn't take anything from the configMap file, even after a restart. Furthermore, the logs show those loaded default variables are not from the applied ConfigMap.
I'm trying to set up the AWS S3 backup. To do so, I have used the ConfigMap from this URL -> https://github.com/zalando/postgres-operator/blob/master/manifests/configmap.yaml. It seems the operator doesn't take anything from the configMap file, even after a restart. Furthermore, the logs show those loaded default variables are not from the applied ConfigMap.
FYI, the operator was installed with Helm