[Documentation] Add upgrade procedure from community to enterprise #1596
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
jwierzbo
reviewed
Feb 21, 2024
| The actual upgrade procedure follows exactly the same steps as | ||
| described above for a simple version upgrade in a sequential manner. | ||
|
|
||
| Regardless of if you are not only changing the images of community and |
There was a problem hiding this comment.
We should mention that the operator image should be changed as well (community -> enterprise). So operator deployment needs to be updated too.
There was a problem hiding this comment.
Not needed, Operator CE will handle ArangoDB EE
ajanikow
approved these changes
Feb 21, 2024
ajanikow
changed the title
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.
Upgrade procedure to enterprise from community