Which image of the operator are you using? e.g. ghcr.io/zalando/postgres-operator:v1.12.2
ghcr.io/zalando/postgres-operator:v1.12.2
Where do you run it - cloud or metal? Kubernetes or OpenShift? [AWS K8s | GCP ... | Bare Metal K8s]
GCP
Are you running Postgres Operator in production? [yes | no]
Not yet
Type of issue? [Bug report, question, feature request, etc.]
Feature Request
Unfortunately at the moment secretAnnotations are not supported in the postgresql cluster manifest.
Would it be possible to include them please? I would like to be able to sync my secrets to a different namespace using the emberstack kubernetes-reflector https://github.com/emberstack/kubernetes-reflector, unfortunately this requires the ability to add secretAnnotations.
Which image of the operator are you using? e.g. ghcr.io/zalando/postgres-operator:v1.12.2 ghcr.io/zalando/postgres-operator:v1.12.2
Where do you run it - cloud or metal? Kubernetes or OpenShift? [AWS K8s | GCP ... | Bare Metal K8s] GCP
Are you running Postgres Operator in production? [yes | no] Not yet
Type of issue? [Bug report, question, feature request, etc.] Feature Request
Unfortunately at the moment secretAnnotations are not supported in the postgresql cluster manifest. Would it be possible to include them please? I would like to be able to sync my secrets to a different namespace using the emberstack kubernetes-reflector https://github.com/emberstack/kubernetes-reflector, unfortunately this requires the ability to add secretAnnotations.
I can see the need for secretAnnotations is also mentioned in https://github.com/zalando/postgres-operator/issues/1736 which was closed with a different outcome due to the specified use case. One comment in this issue https://github.com/zalando/postgres-operator/issues/1736#issuecomment-2120152492 is from another user with the same use case.