removing deprecated namespace option, clarifying docs

Author: SimonBaeumer

cmd/manager/main.go

@@ -3,6 +3,7 @@ package main
 import (
 	"fmt"
 	"os"
+	"sigs.k8s.io/controller-runtime/pkg/cache"
 
 	mdbv1 "github.com/mongodb/mongodb-kubernetes-operator/api/v1"
 	"github.com/mongodb/mongodb-kubernetes-operator/controllers"
@@ -82,7 +83,9 @@ func main() {
 
 	// Create a new Cmd to provide shared dependencies and start components
 	mgr, err := manager.New(cfg, manager.Options{
-		Namespace: watchNamespace,
+		Cache: cache.Options{
+			Namespaces: []string{watchNamespace},
+		},
 	})
 	if err != nil {
 		log.Sugar().Fatalf("Unable to create manager: %v", err)

docs/architecture.md

@@ -10,7 +10,7 @@ The MongoDB Community Kubernetes Operator is a [Custom Resource Definition](http
 
 ## Cluster Configuration
 
-You create and update MongoDBCommunity resources by defining a MongoDBCommunity resource definition. When you apply the MongoDBCommunity resource definition to your Kubernetes environment, the Operator:
+You create and update MongoDBCommunity resources by defining a MongoDBCommunity resource definition in the namespace watched by the operator. When you apply the MongoDBCommunity resource definition to your Kubernetes environment, the Operator:
 
 1. Creates a [StatefulSet](https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/) that contains one [pod](https://kubernetes.io/docs/concepts/workloads/pods/pod-overview/) for each [replica set](https://www.mongodb.com/docs/manual/replication/) member.
 1. Writes the Automation configuration as a [Secret](https://kubernetes.io/docs/concepts/configuration/secret/) and mounts it to each pod.

docs/contributing.md

@@ -69,7 +69,7 @@ to be able to run properly. Create a json file with the following content:
 
 #### Config Options
 
-1. `namespace` is the namespace that will be used by scripts/tooling. All the resources will be deployed here.
+1. `namespace` is the watch namespace of the operator, only in this namespace `MongoDBCommunity` are being reconciled. Additionally, this namespace will be used by scripts/tooling. All the resources will be deployed here.
 2. `repo_url` the repository that should be used to push/pull all images.
 3. `operator_image` will be used as the name of the operator deployment, and the name of the operator image when build.
 4. `e2e_image` the name of e2e test image that will be built.