-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Community operator should support multiple namespaces out of the box #361
Comments
I do agree that it makes little sense to restrict the cluster operator under a single namespace only. This is not how other popular operators, such as https://github.com/zalando/postgres-operator are implemented. Is there a reason, why this design choice was made? |
Same here, this design seems unusual. |
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. |
/no-stale please. |
I also would like ask not to close and make stale. |
Good day!
I installed the operator into namespace
mongodb-operator
with all the defaults settings.I created ns
database
where I put the sample mongodb description.Expected behaviour
The DB is created under custom namespaces with default settings of the operator.
Observed behaviour:
DB is not created at all. If I reinstall operator with
operator.watchNamespace: "*"
the process starts, but then:I checked the helm chart and it looks like that SA for DB management should be present in any namespace where mongodb would be created. It would be nice if operator could take the management of this SA (yes, I want it to have a cluster role to be able to manage all NSs).
The text was updated successfully, but these errors were encountered: