Online image change: handle upgrade of the operator #145
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
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 adds upgrade logic for VerticaDB created from older versions of the operator. We changed the selector label for pods in the sts. The selector label is immutable, so in order to upgrade to the 1.3.0 release, the sts and their pods need to be destroyed. This is handled automatically by a new reconcile actor.
This means that when upgrade to the 1.3.0 release, any running Vertica instance will be stopped then restarted since deleting sts will cause the pods to go away.
A new github workflow was added so that we can change operator pod upgrades going forward.