fix: add kubectl patch to ensure the metric is update successfully - #1105
Merged
Conversation
|
ihcsim
previously approved these changes
Aug 14, 2026
Signed-off-by: pohanhuang <pohan.huang@suse.com>
Contributor
Author
|
@jillian-maroket I just resolve all of the comments above, thanks for the review, can you help review when you are available? |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Problem:
After upgrading from v1.7.x to v1.8.x, the Migration Memory Transfer Rate panel in the VM migration details Grafana dashboard fails to display data due to an outdated metric expression in the dashboard ConfigMap.
Solution:
Add a workaround section to the upgrade doc that patches the dashboard ConfigMap with the correct metric expression.
Related Issue(s):
harvester/harvester#11390
Result