# Is singleNamespace overridable in Percona Posgresql Operator helm chart

**URL:** <https://forums.percona.com/t/is-singlenamespace-overridable-in-percona-posgresql-operator-helm-chart/15367>\
**Category:** Percona Operator for PostgreSQL\
**Created:** [April 24, 2022, 5:33am UTC](https://forums.percona.com/t/is-singlenamespace-overridable-in-percona-posgresql-operator-helm-chart/15367 "2022-04-24T05:33:02Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![A\_Niu](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/a_niu/32/5518_2.png) [@A\_Niu](https://forums.percona.com/u/A_Niu)\
**Post date:** [April 24, 2022, 5:33am UTC](https://forums.percona.com/t/is-singlenamespace-overridable-in-percona-posgresql-operator-helm-chart/15367/1 "2022-04-24T05:33:02Z")

</div>

In CrunchyData pgo helm chart, default value of singleNamespace is false to allow Postgresql Cluster to be in different namespaces. But I cannot find it in Percona Postgres Operator chart values.

Please advise.

Regards,  
Arthur

---

<div class="post-metadata">

**Author:** ![Sergey\_Pronin](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/sergey_pronin/32/14887_2.png) [@Sergey\_Pronin](https://forums.percona.com/u/Sergey_Pronin)\
**Post date:** [May 16, 2022, 10:22am UTC](https://forums.percona.com/t/is-singlenamespace-overridable-in-percona-posgresql-operator-helm-chart/15367/2 "2022-05-16T10:22:26Z")

</div>

Hello @A_Niu ,

what is the goal that you want to achieve with this variable?  
The way we work with single-tenant vs multi-tenant environments is a bit different to what Crunchy has.

Update:  
I just checked and I see that it is not possible to deploy an Operator in one namespace and have cluster in another (or others) with Helm.  
We have this in our template:

```auto
{{- $namespace_fields := list "namespace" "pgo_operator_namespace" }}
...
{{- if has $index $namespace_fields }}
{{ $index | indent 2 }}: {{ $namespace | quote }}

```

So setting `--namespace` in helm chart will change it for both `namespace` and `pgo_operator_namespace` settings in operator.yaml.

I raised the ticket for our eng team to think about it: [[K8SPG-215] Granular namespaces control for operator - Percona JIRA](https://jira.percona.com/browse/K8SPG-215)

---

<div class="post-metadata">

**Author:** ![A\_Niu](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/a_niu/32/5518_2.png) [@A\_Niu](https://forums.percona.com/u/A_Niu)\
**Post date:** [May 16, 2022, 8:54pm UTC](https://forums.percona.com/t/is-singlenamespace-overridable-in-percona-posgresql-operator-helm-chart/15367/3 "2022-05-16T20:54:41Z")

</div>

Thanks @Sergey_Pronin

I found below value to disable the default namespace operating mode to avoid the operator from impacting each other:

```auto
    namespace_mode = "disabled"

```