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

Update metabase chart to use existingSecret pattern #22

Open
themightychris opened this issue Feb 16, 2023 · 0 comments
Open

Update metabase chart to use existingSecret pattern #22

themightychris opened this issue Feb 16, 2023 · 0 comments

Comments

@themightychris
Copy link
Member

Helm charts these days, instead of having you input secret values as helm values, often use existingSecret keys to pull values out of secrets that are assumed to be put into place out of band.

The metabase values file currently postgresql connection details as values: https://github.com/JarvusInnovations/infra-components/blob/main/charts/metabase/values.yaml#L42:L53

The existingSecret file should be expected to have POSTGRES_USER and POSTGRES_PASSWORD keys and pull from there for both configuring the provisioned database and configuring metabase to connect to it. All the other fields can/should stay values

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

No branches or pull requests

1 participant