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

Add more options to pass configuration values #3165

Open
vflaux opened this issue Apr 2, 2024 · 0 comments
Open

Add more options to pass configuration values #3165

vflaux opened this issue Apr 2, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@vflaux
Copy link

vflaux commented Apr 2, 2024

Feature request:

Currently the components are configured by a single config file. I would like to be able to configure them via additional files or environment variables.
When deployed on a kubernetes cluster with the helm chart you currently need to set all the configurations (db hostname, passwords etc.) at install (or template) which is impracticable if you do not know theses values at that time.
Adding other ways to set theses variables would allow to get them from other configmaps or secrets which could be set afterward/asynchronously.

Use case:

We deploy all our manifests via flux and use AWS ACK controllers to provision the database with a custom resource. We do not know the database hostname until the database is created and it is then impossible the properly set the values for helm.
Moreover the database and redis secrets are stored in Secrets (managed by External Secrets) and again, cannot be passed to helm.

@vflaux vflaux added the enhancement New feature or request label Apr 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant