You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As far as I understood from the documentation, when setting user stuff in a cluster manifest (with user access to the database), a secret with login credentials will be created in the same namespace where the cluster is deployed. But what if we want to access the database from other namespaces?
Use Case
I would like to deploy database clusters in different namespaces than the ones from where the apps accessing them are running. So, it would be great that we could set in which namespaces the secrets with the login credentials are created.
Desired Behavior
We could define in which namespaces the login credentials secrets are created in our cluster manifests.
Environment
This feature would be environment agnostic. You would only need different namespaces in which databases and applications using these databases are deployed.
Additional Information
Right now I'm just copying secrets between namespaces. I would like to avoid this step as I think is error prone, and also a bit insecure.
The text was updated successfully, but these errors were encountered:
Overview
As far as I understood from the documentation, when setting user stuff in a cluster manifest (with user access to the database), a secret with login credentials will be created in the same namespace where the cluster is deployed. But what if we want to access the database from other namespaces?
Use Case
I would like to deploy database clusters in different namespaces than the ones from where the apps accessing them are running. So, it would be great that we could set in which namespaces the secrets with the login credentials are created.
Desired Behavior
We could define in which namespaces the login credentials secrets are created in our cluster manifests.
Environment
This feature would be environment agnostic. You would only need different namespaces in which databases and applications using these databases are deployed.
Additional Information
Right now I'm just copying secrets between namespaces. I would like to avoid this step as I think is error prone, and also a bit insecure.
The text was updated successfully, but these errors were encountered: