[node] add option to generate node keys #365
Merged
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 chart already has the
persistGeneratedNodeKey
option to generate node keys. These keys are random and stored on disk. They are not known before deployment, so they cannot be used for testnet bootnode deployments.Changes:
--node-key $(cat /path/to/key)
with--node-key-file /path/to/key
. This is more secure, as the key is not exposed in theps
output.cat
was previously used to fix the newline issue at the end of the file. Keys stored in Helm secrets do not have a trailing newline.