Helm chart deployment

[Jean-Baptiste_PIN]

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…

[Sergey_Pronin]

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 create the namespace:

percona/percona-helm-charts/blob/main/charts/psmdb-operator/templates/namespace.yaml

and it does not make sense.

[Jean-Baptiste_PIN]

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

[ORich]

Helm chart psmdb-operator 1.13.0 - Not aligned with the rest of 1.13.0

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_STRUCTURED value: 'false' - name: DISABLE_TELEMETRY value: "false"