-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tezos-proto-cruncher chart #532
Merged
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
This chart deploys a daemonset in your cluster. the daemonset runs a parallel search for a vanity protocol hash. It takes s3 bucket credentials. Protocol is downloaded from bucket then results are written to the bucket. It does not terminate: it keeps running until the cluster is torn down.
harryttd
requested changes
Jan 24, 2023
Suggestion: explain how to uninstall the chart in the medium article when it isn't needed anymore |
Co-authored-by: Aryeh Harris <harryttd@users.noreply.github.com>
harryttd
reviewed
Jan 25, 2023
harryttd
approved these changes
Jan 26, 2023
Sachito18
added a commit
to smart-chain-fr/tezos-k8s
that referenced
this pull request
Jan 27, 2023
* Exit config-init script on error (oxheadalpha#531) * Exit config-init script on error * Update chart tests * Set fitness to 1 instead of -1 at activation (oxheadalpha#534) A bug was uncovered during mumbai activation, where nodes were unable to activate and were crashing. The [fix](https://gitlab.com/tezos/tezos/-/merge_requests/7462/diffs) broke dailynet because it is no longer possible to activate with a fitness of -1 (which is how we have been activating chains since the beginning of tezos-k8s). Replacing this value to 1 fixes the issue for dailynet and also does not appear to be causing any issue with v15.1. * tezos-proto-cruncher chart (oxheadalpha#532) * tezos-proto-cruncher chart This chart deploys a daemonset in your cluster. the daemonset runs a parallel search for a vanity protocol hash. It takes s3 bucket credentials. Protocol is downloaded from bucket then results are written to the bucket. It does not terminate: it keeps running until the cluster is torn down. * better variable names * Update charts/tezos-proto-cruncher/scripts/proto-downloader.py Co-authored-by: Aryeh Harris <harryttd@users.noreply.github.com> * address review comments * lint python scripts with black * catch exception when s3 upload fails * fix manual method * fix manual method, better way per Aryeh * fail fast when env vars not set in proto downloader Co-authored-by: Aryeh Harris <harryttd@users.noreply.github.com> Co-authored-by: Aryeh Harris <harryttd@users.noreply.github.com> Co-authored-by: Nicolas Ochem <nicolas.ochem@gmail.com>
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.
This chart deploys a daemonset in your cluster. the daemonset runs a parallel search for a vanity protocol hash.
It takes s3 bucket credentials. Protocol is downloaded from bucket then results are written to the bucket.
It does not terminate: it keeps running until the cluster is torn down.