small fixes to make helm build more resilient #60
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.
The following small fixes were required to build the helm chart successfully on an Ubuntu 22.04 machine with helm 3.11.3:
With the fixes, the helm chart builds and deploys correctly (not tested with the controller, that's subject for a next PR)
Test protocol for reproducing the problems this PR claims to fix:
make helm-clean
followed bymake helm
to ensure a clean environmentmake helm-keylime-deploy
to test the built chartvalues.yaml
is mostly indifferent, corresponds to the first default in the README