secretNamespace type

[apena-pmy]

• Which image of the operator are you using?
  • registry.opensource.zalan.do/acid/postgres-operator:v1.8.1
• **Where do you run it ?
  • Bare Metal K8s]
• Are you running Postgres Operator in production?
  • No
• Type of issue?
  • feature request

We deployed a PostgreSQL database in namespace A and we need the _owner _writer and _reader secrets in more than one another namespace.
Is it posible to change the secretNamespace type from string to array ??

[FxKu]

If we would allow the same secrets to be stored in multiple namespaces we would need to re-work the whole syncing process of secrets (incl. rotation of credentials inside secrets). I think neither is this something we want now is it good practice in K8s in general. Why can't all your apps (living in different namespaces, I guess) refer the to same secret namespace?

[apena-pmy]

Thanks @FxKu for your reply.
Yes, we have our apss in different namespaces and need them to access the PostgreSQL databases.
I'm not sure what you mean with "refere the to same secret namespace" as secrets could not be access from another namespace in k8s.