[patch] During grafana update, get storage config from v4. #1274
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
stonepd
requested review from
durera,
andrercm,
sanjayprab,
terenceq and
whitfiea
as code owners
whitfiea
approved these changes
Apr 17, 2024
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.
Fixing Issue https://jsw.ibm.com/browse/MASCORE-2363
Modify the Grafana update to get the V5 storage class and size from the V4 config and reuse the same values.
This also fixes the Grafana V5 persistent storage configuration which was previously incorrectly set, resulting in grafana deployments with no persistent storage
Tested in personal FVT environment