Deployment only works in the same namespace where the operator was installed about mongodb-kubernetes-operator HOT 5 CLOSED

I encountered issues as well. What you need to do is documented as part of the enterprise operator, which I found in another issue.

The reason you encounter issues is because the operator assumes certain resources to exist and does not deploy them for you. It's not very intuitive. Here's the documentation for setting the scope of the operator: https://www.mongodb.com/docs/kubernetes-operator/master/tutorial/set-scope-k8s-operator/#ns-scope-different-ns

What you need to do is deploy a subset of resources from the the operator chart in every namespace where you want to deploy MongoDBCommunity resources:

helm template mongodb/enterprise-operator \
  --set operator.namespace=<metadata.namespace> \
  --show-only templates/database-roles.yaml | kubectl apply -f -

This creates the missing service account, role and role binding needed by the pods.

from mongodb-kubernetes-operator.

I used the following command, to try to configure the deployment in a different namespace:

kubectl apply -k config/rbac --namespace <my-namespace>

Using the files available here, and it still didn't work.

I followed the steps as described here:
https://github.com/mongodb/mongodb-kubernetes-operator/blob/master/docs/install-upgrade.md#install-in-a-different-namespace-using-kubectl

from mongodb-kubernetes-operator.

This issue is being marked stale because it has been open for 60 days with no activity. Please comment if this issue is still affecting you. If there is no change, this issue will be closed in 30 days.

from mongodb-kubernetes-operator.

This issue was closed because it became stale and did not receive further updates. If the issue is still affecting you, please re-open it, or file a fresh Issue with updated information.

from mongodb-kubernetes-operator.