Postgres Operator setup for Kubernetes cluster

• Which image of the operator are you using? e.g. ghcr.io/zalando/postgres-operator:v1.12.2
• Where do you run it - cloud or metal? Kubernetes or OpenShift? K8s
• Are you running Postgres Operator in production? yes
• Type of issue? question

Hi,

We are using the Postgres Operator in a setup where we have a lot of different users on a Kubernetes cluster with some isolation level applied.
This means each user might have multiple Postgres instances running in one or multiple namespaces.

Now my question is, what is the best approach for deploying the Postgres Operator in such a case:

1. Should every Postgres instance have its own Operator running (could be multiple Operators in one namespace)
2. Install a cluster-wide Postgres Operator to manage all Postgres instances across all namespaces
3. Create one Operator per each namespace (so max one Operator in a namespace but possibly multiple Postgres instances)

The issue names no files, tests, or entry points. Review the operator's deployment and namespace-scope guidance, then compare the three proposed installation models; this is done when maintainers document the supported approach and its isolation or operational constraints.