[node] add tpl to init containers #333
Merged
Conversation
This file contains 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
lazam
approved these changes
Mar 21, 2024
|
Could you add a test of an example custom chainspec in the |
BulatSaif
force-pushed
the
bs/update-node-helmchart
branch
from
63e06d4 to
8ed5521
Compare
I added |
PierreBesson
approved these changes
Mar 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
There are situations when it is useful to run a node with a custom chainspec. In the current approach, you need to generate the chainspec, upload it, and set
CustomChainspecUrl, or you need a custom binary. An alternative approach is to use an init container to generate and store the chain-spec in/chain-data/chainspec.json. In this PR, I added some changes which may be useful for doing so. It is now possible to mount a custom chainspec as a configmap as well.Changes: