You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per the title, this is a follow up to an issue I encountered back in September. I thought that we addressed the issue then, however started to see it again while testing a new PR.
The Charts side (that ships the fix): rancher/charts#4872
Chart RC to test: PromFed 105.1.0-rc.1+up0.4.5-rc.1
Note: expected container image is: v0.4.4-rc.2
While this issue was improved in the mentioned chart and PromFed version. The root issue is related to the version of Rancher Project Monitoring in use. And the version that the referenced tag above uses isn't going to use this.
So the updated/patched value could be validated, but won't be fully used until later PRs. As such the issue should probably be validated and tested with those later PRs. Nothing in the previous mentioned tag/RC will actually be worth validating this bug on until then.
Per the title, this is a follow up to an issue I encountered back in September. I thought that we addressed the issue then, however started to see it again while testing a new PR.
The background of how I found the issue is here: rancher/rancher#47155
The gist:
0.3.x
ofrancher-project-monitoring
,0.4.x
project mon) where Monitoring is installed,grafana.defaultDashboards.useExistingNamespace: true
should be set.As such this issue is to track applying that fix to the actual project monitoring chart.
After the fix, this value should be
true
by default and not need manual setting.The text was updated successfully, but these errors were encountered: