ci: compress genesis file during deployment #2512
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
During ramp-up to Testnet 52 (#2415), we opportunistically updated the Discord allocations, and encountered #1783 again. While we need a durable solution to that problem, we also want a quick fix, so we turn to tried-and-true file compression: we gzip the generated json file, base64 encode it to sideload it into the cluster, then decompress it as part of the initContainer bootstrapping logic during node creation. This is a "good enough" solution to buy time for the near future, ensuring that we can continue to update Discord allocations when we want. The compression ratio is approximately 3x, which gives us some headroom.
conorsch
added a commit
that referenced
this pull request
May 9, 2023
Follow-up to #2512. Here we remove the ConfigMap generation from the Helm logic, opting instead to create/delete the resource manually via direct use of `kubectl`. This removes the large base64-encoded file from the Helm manifest, sidestepping the 1MB limit. We're still subject to a 1MB limit on the ConfigMap object itself, but the gzipped-then-base64d data is ~590Kb right now, so we've got some more time.
conorsch
added a commit
that referenced
this pull request
May 9, 2023
Follow-up to #2512. Here we remove the ConfigMap generation from the Helm logic, opting instead to create/delete the resource manually via direct use of `kubectl`. This removes the large base64-encoded file from the Helm manifest, sidestepping the 1MB limit. We're still subject to a 1MB limit on the ConfigMap object itself, but the gzipped-then-base64d data is ~590Kb right now, so we've got some more time.
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.
During ramp-up to Testnet 52 (#2415), we opportunistically updated the Discord allocations, and encountered #1783 again. While we need a durable solution to that problem, we also want a quick fix, so we turn to tried-and-true file compression: we gzip the generated json file, base64 encode it to sideload it into the cluster, then decompress it as part of the initContainer bootstrapping logic during node creation. This is a "good enough" solution to buy time for the near future, ensuring that we can continue to update Discord allocations when we want. The compression ratio is approximately 3x, which gives us some headroom.