Ability to use secrets as environment variables #186
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
In order to improve the security posture of druid installations using helm chart, I propose this change where environment variables can be set using kubernetes secrets.
This would be useful, for example, when configuring a Postgres extension where one needs to provide credentials.
Example of usage:
I'm opening as a draft to get initial feedback. If you agree with the proposal I'll polish the code and update the docs.
This PR has: