EVEREST-1841 MongoDB Major Version Upgrades #650
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
In order for major version upgrades to work correctly we need FCV enabled. Enabling FCV means that downgrades are not possible. This is not an issue because we are blocking that action in the API and starting from MongoDB 8 this is no longer possible in the community version.
recharte
force-pushed
the
EVEREST-1841-mongodb-major-upgrades
branch
from
ee9dec8 to
ea3fa39
Compare
recharte
force-pushed
the
EVEREST-1841-mongodb-major-upgrades
branch
from
ea3fa39 to
c337ed0
Compare
maxkondr
approved these changes
Feb 20, 2025
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.
MongoDB Major Version Upgrades
Problem:
EVEREST-1841
In order to get a fully automated major version upgrade of MongDB we need to set FCV. This automatically enables the features of the new version after upgrading. The drawback is that we can't downgrade but we are blocking downgrades regardless. More info about the MongoDB major version upgrades can be found here.
I also extended the E2E tests to have a DB upgrade suite (triggered by the
test/e2e-db-upgradelabel). By doing so I changed the label that triggers the operator upgrade tests fromtest/e2e-upgradetotest/e2e-operator-upgrade.Related pull requests
CHECKLIST
Helm chart
[ ] Is the helm chart updated with the new changes? (if applicable)Jira
Tests