Update minikube/openshift upgrade instructions #2383
Conversation
This file contains hidden or 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
sumin-denys
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
This PR updates the Kubernetes upgrade instructions for both Minikube and OpenShift deployments.
These changes align the Kubernetes documentation with the instructions in our Docker Compose documentation, ensuring consistency across platforms.
Changes
Sequential Upgrades: Adds a note emphasizing that upgrades must be performed sequentially, one version at a time (e.g.,$\rightarrow$ $\rightarrow$
4.0.04.0.14.1.0).--fromVersionFlag Usage: Adds an info banner explaining that the--fromVersionflag is mandatory for upgrades to versions prior to3.9.1, providing a specific example.CE to PE Migration: Clarifies the Community Edition (CE) to Professional Edition (PE) migration process. It now explicitly states that the upgrade script must be run with the
--fromVersion=CEflag (Step 4) to correctly migrate the database data.PE
CE
