Open
Conversation
|
Hi @sorvis , I see that you are using ConfigMap for the values of Postgres connection string and the encryption secret. Because this values could be considered "secrets", what do you think about add the option to use "secretKeyRef" if a secret name is configured in values.yml file? This would give the option to the user of Helm chart to use your "ConfigMap" setup or manage these values from a previous secret created in the cluster. |
|
Doesn't need a full helm chart. You can use bjw-s app template |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Added in a helm chart. Tested in our local cluster.