ci: automate chain upgrades on k8s deployments #4477
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
conorsch
force-pushed
the
upgrade-testing-deployment
branch
from
76f7175 to
318b577
Compare
conorsch
changed the title
conorsch
changed the title
cratelyn
added
A-CI/CD
Here's long-needed automation for deploying chain upgrades on Penumbra testnets deployed to k8s. Ideally we'd use an operator pattern to manage the lifecycle, but we're trying to move quickly, so bash it'll be for now. Also included are some lower thresholds for the devnet environment, since it's frequently used for this kind of testing. Might make more sense to create a dedicated "upgrade-testing" environment, but again, prioritizing speed and reliability, so we can circle back on fleshing things out once we hit our deadlines. Tacked on some help scripts, such as "enable-maintenance-mode" and "perform-point-release", which are helpful for managing devnets. debugging devnets.
conorsch
force-pushed
the
upgrade-testing-deployment
branch
from
318b577 to
3c71548
Compare
conorsch
changed the title
cratelyn
approved these changes
May 30, 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.
Describe your changes
These changes record the scripted migration approach that was used for releasing Testnet 76 (#4402). These scripts aren't yet tied into CI workflows, but that's fine: I've been using this scripted flow to deploy chain upgrades, and I want to do that several more times before enshrined it as final in CI. Also includes some foundation for E2E testing of migration flows targeting the cluster.
Issue ticket number and link
Related to testing ask in #4323, although there's more work in progress leveraging these scripts, and thus I want these to land in main.
Checklist before requesting a review
If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason: