Repository navigation
Conversation
Grafana 13 no longer grants the configured Admin role to anonymous users.
Collaborator
|
My friend just telegraphed:
Up to you, though |
theyoprst
approved these changes
Oct 30, 2026
This branch has not been deployed
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
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
metrics-grafanainmonitoring-systemdoes not expose the VictoriaMetrics Prometheus-compatible datasource, leaving Soperator dashboards without metric data.The datasource ConfigMap exists and is discovered by the Grafana sidecar. However, the sidecar’s provisioning reload request returns 403 Forbidden because:
Solution
Enable Basic Auth for provisioning requests while keeping the interactive login form disabled.
Testing
Enabled basic auth on a dev cluster, and restarted Grafana pod.
Release Notes
Fix: Missing data source in Grafana.