Update system-redis internal database from 3.2 to 5.x #617
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
|
Code Climate has analyzed commit 8d96b99 and detected 3 issues on this pull request. Here's the issue category breakdown:
View more on Code Climate. |
Contributor
Author
|
/retest |
eguzki
approved these changes
Jun 8, 2021
Member
|
I still cannot believe that upgrade is just a matter of updating the image. But if it works... let it be. |
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 PR implements changing the used system-redis internal database Redis version from 3.2 to 5.x
This has been done for both templates and operator.
In case of the productized version the image URLs will be different than the upstream ones that are the ones that can be seen in this PR. The productized URLs will be updated/set on the corresponding downstream repository branch/es.
In the operator case it also includes upgrade automation to migrate from one version to another. The upgrade migration includes:
In the templates case upgrade documentation will be needed.