Single percona-server-mongodb-operator deployment watching all namespaces for CRD PerconaServerMongoDB

Dear experts,
working with version 1.7.0, I would like to setup a single percona-server-mongodb-operator deployment watching all namespaces for CRD PerconaServerMongoDB in my k8s cluster.
I tried to update the deploy/operator.yaml file as follows even I did not find any documentation about it yet. I also convert deploy/rbac.yaml from Role to ClusterRole bindings, but it is still not working …
Does anyone try such a setup ? Do you know if this is supported by Percona in 1.7.0 or planed in next releases ? Many thanks in advance.
Kind regards. Richard.

env:
- name: WATCH_NAMESPACE
value: “*”

1 Like

E0510 14:47:50.213745 1 reflector.go:153] sigs.k8s.io/controller-runtime/pkg/cache/internal/informers_map.go:224: Failed to list *v1.PerconaServerMongoDB: perconaservermongodbs.psmdb.percona.com is forbidden: User "system:serviceaccount:psmdb-integ:percona-server-mongodb-operator" cannot list resource "perconaservermongodbs" in API group "psmdb.percona.com" in the namespace "*"

1 Like

Hello ORich, thank you for submitting this.

Our MongoDB Operator does not support cluster-wide mode yet. We have it in our roadmap (JIRA issue, github roadmap issue).
I don’t have any specific ETA for now. As a workaround you can deploy an Operator per namespace and/or run multiple clusters in the same namespace managed by it.

Feel free to share your opinion in github roadmap issue and maybe state the use case. It might generate traction and we would prioritize it in our roadmap.

1 Like