-
Notifications
You must be signed in to change notification settings - Fork 294
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
Load secret info from k8s Secret objects. #319
Comments
Is possible to resolve ENV variables in comm_config.yaml ?
Btw: |
That seems like it would work. Is using environment variables the ideal way to set secrets? |
Have a similar related questions to @lukasmrtvy Can i use an Env variables to overwrite the configMap values? If so, where should i put it? At the Deployment level with the corresponding container env vars ? or at the config level shown above.
|
Any news about this? |
Any news? @ebrianne already solved this here: https://github.com/ebrianne/helm-charts/pull/9 |
If that's fine I can make a PR soon to integrate this into the official chart |
@ebrianne I've added a comment about your solution here: #480 (comment), could you please take a look? |
) ##### ISSUE TYPE - Feature Pull Request ##### SUMMARY I have implemented in the helm chart the possibility to pass the communication config as a k8s secret and configure in the value files via an existingSecret. It can be configured in the values file via these: ```yaml communications: existingSecret: false existingSecretName: "" ``` Fixes #319 #211 #226 #233
Is your feature request related to a problem? Please describe.
I'm using HelmResource CRD objects to install and manage helm v3 packages. Putting a secret in clear text in a HelmResource yaml file, to be committed in a git repository, is a no-no.
Secrets need to be stored separately, ideally in a sealed secret.
Describe the solution you'd like
Instead of storing secret information in the
values.yaml
, thevalues.yaml
should allow pointing at an exist k8s Secret object by name and namespace.Describe alternatives you've considered
There isn't really any way to use the chart with the current design without leaking secrets.
Additional context
I like the project. It looks cool!
The text was updated successfully, but these errors were encountered: