Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Since rancher-project-monitoring 0.4.x grafana.useExistingNamespace should be used #130

Open
mallardduck opened this issue Dec 11, 2024 · 2 comments
Assignees
Labels
bug Something isn't working team/observability&backup
Milestone

Comments

@mallardduck
Copy link
Member

mallardduck commented Dec 11, 2024

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:

  1. For a long time PromFed was locked to ship 0.3.x of rancher-project-monitoring,
  2. When I fixed the build bug that caused that it started to use the newest one,
  3. We encounter this bug on any PromFed install (with embeded 0.4.x project mon) where Monitoring is installed,
  4. To fix the deployment, an override of 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.

@mallardduck
Copy link
Member Author

mallardduck commented Dec 13, 2024

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

@mallardduck mallardduck modified the milestones: v2.11.0, v2.12.0 Dec 17, 2024
@mallardduck
Copy link
Member Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working team/observability&backup
Projects
None yet
Development

No branches or pull requests

1 participant