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.
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.
We have the same usecase. Different teams in different openshift projects want to make use of the same operator installation. We don’t want to maintain various operator installations for the same purpose.
So it would be good if we don’t have to name the namespaces, but use e.g. “*” for all projects.
Furthermore we’re only allowed to install directly from operatorhub, so this would be needed also for cluster-wide installation.
Is there any plan to include this feature in future, e.g. in operator version 2.0?