According to this doc, we have to explicitly list all (already existing) namespaces where we want to deploy pgsql clusters at operator installation step. And we can modify that list later but the operator has to be deleted then re-installed.
Is there a way to make this operator really cluster-wide (meaning available for all namespaces), as it is possible with the XtraDB one as described in this doc by setting an empty list of namespaces ?
Another question related to this cluster-wide mode, is there a limit for the number of namespaces managed by one single operator ? Is this why you write in the doc :
We recommend running Percona Operator for PostgreSQL in a traditional way, limited to a specific namespace.
Hello @edd ,
currently it is not possible to deploy it once and cover all namespaces. You need to specify namespaces explicitly.
We will research how hard is it to provide this feature.
What is blocking you currently to specify namespaces?
Thanks for your answer.
We’re working on a shared Openshift cluster between different teams and projects and we’d like to be able to provide a cluster-wide operator in the marketplace (dev catalog in Openshift) to already existing but also to future new projects that are regularly created on the cluster, without having to reinstall the operator each time a new project is added.
As far as I understood, this is how XtraDB operator works for MySQL or even the Crunchy Data operator for Postgres and we’re looking for the same kind of feature with your operator.