Bring my own secret for postgresql connection #27916
AurimasNav
started this conversation in
General
Replies: 2 comments
-
it works fine with adding ingore diffs to argocd application: ignoreDifferences:
- kind: Secret
name: superset-env
namespace: superset
jsonPointers:
- /data/DB_HOST
- /data/DB_NAME
- /data/DB_PASS
- /data/DB_USER however I would still prefer a way to specify my own secret for postgresql connection paramaters. |
Beta Was this translation helpful? Give feedback.
0 replies
-
The following configuration works for us:
You can then create your own secret, but this must have the name superset-env. The secret must contain all the values that are otherwise defined in https://github.com/apache/superset/blob/master/helm/superset/templates/secret-env.yaml. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I want to configure external postgresql to work with superset, however doing it in helm values does not work well with GitOps since I don't want to have my username/pass in git. I can provision my own secret, but I don't see a way to tell helm chart to use it for env vars for this purpose.
I have also tried to merge the existing secret with new values (using external-secrets) which would work in theory, but argocd syncs it back to original values.
Any suggestions to do it properly with argocd+external-secrets if there is no native way to configure it via helm?
Beta Was this translation helpful? Give feedback.
All reactions