Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

controlPlane.backingStore.database.external.dataSource should be able to be read from a Secret #1755

Open
virtualdxs opened this issue May 8, 2024 · 1 comment

Comments

@virtualdxs
Copy link

Is your feature request related to a problem?

I use the cloudnative-pg operator to deploy Postgres databases in my Kubernetes host cluster. It automatically creates a Secret with the credentials and endpoint information of how to connect to the Postgres database, as is common. I would like to be able to tell vCluster to get its database connection information from that secret.

This allows me to never need to store the database password in my configuration repository. As it stands, I must store the database password unencrypted in the values.yaml for the Helm release.

Which solution do you suggest?

Support specifying an existingSecret to retrieve this information from. To use the Nextcloud helm chart as an example:

existingSecret:
  enabled: false
  # secretName: nameofsecret
  usernameKey: db-username
  passwordKey: db-password
  # hostKey: db-hostname-or-ip
  # databaseKey: db-name

This example uses separate keys for username, password, etc. but just being able to retrieve the uri from a secret would be sufficient

Which alternative solutions exist?

Allow in the Helm chart for a custom config-secret to be specified so I can use SOPS to securely store it encrypted in my configuration repository

Additional context

No response

@heiko-braun
Copy link
Contributor

Thanks, it's a reasonable request and we are already looking into it. Unfortunately, I don't have any concrete dates yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants