You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
4. Review the possible Operator [deployment scopes](#understand-mongodb-community-operator-deployment-scopes) and configure the Operator to watch other namespaces, if necessary.
25
+
26
+
### Understand Deployment Scopes
27
+
28
+
You can deploy the MongoDB Community Kubernetes Operator with different scopes based on where you want to deploy MongoDB resources:
29
+
30
+
-[Operator in Same Namespace as Resources](#operator-in-same-namespace-as-resources)
31
+
-[Operator in Different Namespace Than Resources](#operator-in-different-namespace-than-resources)
32
+
33
+
#### Operator in Same Namespace as Resources
34
+
35
+
You scope the Operator to a namespace. The Operator watches MongoDB resources in that same [namespace](https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/).
36
+
37
+
This is the default scope when you install the Operator using the [installation instructions](#procedure).
38
+
39
+
#### Operator in Different Namespace Than Resources
40
+
41
+
You scope the Operator to a namespace. The Operator watches MongoDB resources in other namespaces.
42
+
43
+
To configure the Operator to watch resources in other namespaces:
44
+
45
+
1. In the Operator [resource definition](../deploy/operator/operator.yaml), set the `WATCH_NAMESPACE` environment variable to one of the following values:
46
+
47
+
- the namespace that you want the Operator to watch, or
48
+
-`*` to configure the Operator to watch all namespaces in the cluster.
0 commit comments