Skip to content
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

Open
gecube opened this issue Nov 13, 2024 · 5 comments
Open

Community operator should support multiple namespaces out of the box #361

gecube opened this issue Nov 13, 2024 · 5 comments

Comments

@gecube
Copy link

gecube commented Nov 13, 2024

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:

  Normal   SuccessfulCreate  6m26s                 statefulset-controller  create Claim data-volume-call-analytics-mongodb-0 Pod ***-mongodb-0 in StatefulSet call-analytics-mongodb success
  Normal   SuccessfulCreate  6m26s                 statefulset-controller  create Claim logs-volume-call-analytics-mongodb-0 Pod ***-mongodb-0 in StatefulSet call-analytics-mongodb success
  Warning  FailedCreate      58s (x17 over 6m26s)  statefulset-controller  create Pod call-analytics-mongodb-0 in StatefulSet ***-mongodb failed error: pods "call-analytics-mongodb-0" is forbidden: error looking up service account databases/mongodb-database: serviceaccount "mongodb-database" not found

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).

@WiZeYAR
Copy link

WiZeYAR commented Nov 27, 2024

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?

@antoineozenne
Copy link

Same here, this design seems unusual.

LucaDev added a commit to LucaDev/Home that referenced this issue Dec 28, 2024
Copy link
Contributor

github-actions bot commented Feb 8, 2025

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.

@github-actions github-actions bot added the Stale label Feb 8, 2025
@antoineozenne
Copy link

/no-stale please.

@github-actions github-actions bot removed the Stale label Feb 9, 2025
@gecube
Copy link
Author

gecube commented Feb 9, 2025

I also would like ask not to close and make stale.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants