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.
This PR replaces #24
Background
When reviewing this project I found the setup details off-putting. I felt a Helm chart would make it simpler to install the software. It would also automate:
Motivation
I am considering utilizing Tesoro as a better (gitops compatible) secret management solution. I like how embedded references encode all the details of accessing the secret. The only comparable solution. in my option, would be External Secrets.
While I acknowledge the authors use kapitan to do their manifest generation, in our case we use Helm to install our cluster's platform services.
Enhancements
Known issues
This helm chart will not work on Kubernetes v1.19
Latest version of helm is using go 1.14