-
Notifications
You must be signed in to change notification settings - Fork 381
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] Grafanafolders permissions not synced #1127
Comments
Update:
So it looks like permissions won't be synced for the new grafana pod. |
@oleksii-kalinin could you share your grafana setup? We don't have any We need to troubleshoot this a bit more before being able to merge your PR. |
Hi. resyncPeriod described in the API docs https://grafana-operator.github.io/grafana-operator/docs/api/#grafanafolderspec Manifests:
Grafana Folder CR
Grafana is fully stateless. The possible reason I've found: the operator can and will sync permissions to the first created grafana pod. The operator won't sync permissions to the new pod. |
Describe the bug
Permissions are set via
spec.permissions
for theGrafanaFolder
CR. Permissions are not synced with the folders after 10m.Version
v5.0.2
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Permissions are set to the folder right after sync.
Suspect component/Location where the bug might be occurring
GrafanaFolder
Screenshots
Wrong permission:
Default permissions are applied even if
spec.permissions
setRuntime (please complete the following information):
Additional context
Logs
Full grafanafolder manifest
If I completely delete NS where operator and grafana deployed and redeploy - everything becomes ok.
The text was updated successfully, but these errors were encountered: