One kubeseal instance to manage secrets in a subset of namespaces

Hello,

I'm looking for a solution like `kubeseal` to `encrypt/decrypt` on the fly our kubernetes secrets to allow us to put all of them into a git repository _(helm chart)_.

So I followed the recent Improvements made on the tool like the ability to deploy `kubeseal` into a single namespace and to configure it to **not watch** secrets in all namespace _(flag: --all-namespaces=false)_.

**Now my question is:**

We are sharing a kubernetes cluster _(we are restricted in namespaces that we owned, no admin access on the cluster)_ and we have applications in different namespaces. Can we have a kubeseal instance deployed on a dedicated namespace and tell him to manage `encryption/decryption` of secrets located in different namespaces _(not all namespaces but a list of allowed namespaces)_ or Do I need to deploy a kubeseal controller on each namespace and switch between all of them when I want to encrypt a secret _(because I think not the same encryption key pair is used)_?

Thanks you for your reply

The issue names no files, tests, or entry points. Start by reviewing the controller's namespace-watch configuration and the --all-namespaces=false deployment behavior; done means determining whether one instance can manage an explicit subset of namespaces with one encryption key, or whether separate controllers are required.

Written by the indexing model from the issue text.