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

**URL:** <https://forums.percona.com/t/single-percona-server-mongodb-operator-deployment-watching-all-namespaces-for-crd-perconaservermongodb/10376>\
**Category:** Percona Operator for MongoDB\
**Created:** [May 7, 2021, 10:27am UTC](https://forums.percona.com/t/single-percona-server-mongodb-operator-deployment-watching-all-namespaces-for-crd-perconaservermongodb/10376 "2021-05-07T10:27:07Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ORich](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/orich/32/7918_2.png) [@ORich](https://forums.percona.com/u/ORich)\
**Post date:** [May 7, 2021, 10:27am UTC](https://forums.percona.com/t/single-percona-server-mongodb-operator-deployment-watching-all-namespaces-for-crd-perconaservermongodb/10376/1 "2021-05-07T10:27:07Z")

</div>

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: “\*”

---

<div class="post-metadata">

**Author:** ![ORich](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/orich/32/7918_2.png) [@ORich](https://forums.percona.com/u/ORich)\
**Post date:** [May 10, 2021, 2:52pm UTC](https://forums.percona.com/t/single-percona-server-mongodb-operator-deployment-watching-all-namespaces-for-crd-perconaservermongodb/10376/2 "2021-05-10T14:52:30Z")

</div>

`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 "*"`

---

<div class="post-metadata">

**Author:** ![Sergey\_Pronin](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/sergey_pronin/32/14887_2.png) [@Sergey\_Pronin](https://forums.percona.com/u/Sergey_Pronin)\
**Post date:** [May 12, 2021, 1:30pm UTC](https://forums.percona.com/t/single-percona-server-mongodb-operator-deployment-watching-all-namespaces-for-crd-perconaservermongodb/10376/3 "2021-05-12T13:30:29Z")

</div>

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](https://jira.percona.com/browse/K8SPSMDB-203), [github roadmap issue](https://github.com/percona/roadmap/issues/42)).  
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](https://github.com/percona/roadmap/issues/42) and maybe state the use case. It might generate traction and we would prioritize it in our roadmap.