Hi there, I’m wondering why the chart create the namespace that is given on watchNamespace ? This should not be the chart responsibility to create the namespace. I do install it with argocd and everytime I’m updating the deployment, the namespace is deleted… loosing my data etc…

Frankly speaking for MongoDB Operator watchNamespace flag does not make any sense. It does not support cluster-wide (multi-namespace deployment) mode yet, but it is coming in version 1.13. So for now the best way would be to skip this flag. But looking at our yaml manifest I see that we indeed cr…

Also the cronjob is created with Service Account: percona-server-mongodb-operator But the helm chart never create this service account nor the rbac?

[image] Helm chart psmdb-operator 1.13.0 - Not aligned with the rest of 1.13.0 Percona Operator for MongoDB Chart 1.13.0 looks not supporting cluster wide deployment as well as Deployment rendered by chart is missing here under env variables env: - name: LOG_S…

Helm chart deployment

MongoDB Percona Operator for MongoDB

ORich September 27, 2022, 8:53am 4

Topic		Replies	Views
Missing key "meta.helm.sh/release-namespace": must be set Percona Operator for MongoDB	2	5749	March 21, 2022
Helm chart psmdb-operator 1.13.0 - Not aligned with the rest of 1.13.0 Percona Operator for MongoDB	3	754	September 28, 2022
Single percona-server-mongodb-operator deployment watching all namespaces for CRD PerconaServerMongoDB Percona Operator for MongoDB	2	1174	May 12, 2021
Installing with official helm charts in dedicated namespace failing Percona Server for MongoDB	3	879	July 16, 2024
Failed to create MongoDB operator and DB cluster in different namespaces Percona Operator for MongoDB	11	1508	January 27, 2022

Helm chart deployment

Related topics