Closed zamanh closed 1 month ago
Can you verify that a folder with this UID exists in the Grafana instance? If so, does restarting the operator pod fix the issue?
Can you verify that a folder with this UID exists in the Grafana instance? If so, does restarting the operator pod fix the issue?
Folder exists
However alert fails to apply in the same way specified in the bug.
I have attempted to restart the operator however there appears to be no difference.
From what I can conclude, my team members and I figured that if you put the alerts into a folder which has the same name as its namespace, it doesn't appear to handle it well. This is the UID of the folder (which is named like the namespace)
This is the error on one of the Grafanaalertrulegroups
Yeah this is an interesting edge-case. This is what happens:
There is a way to resolve this in the upcoming update
folderRef
(this is not yet released)This way, the folder resource has full control over the UID and matching will work as expected
We'll release a new version soon - would love to hear back once you updated and tried the new aproach
I'm also experiencing similar behaviour. If you delete the ARG (kubectl delete grafanaalertrulegroup
) and apply it again, it's able to find the folder's uid, and is applied successfully.
Looking forward to a fix.
The fix for this has been released in v5.11 - see my previous comment on how to resolve this in the new version
Hi @theSuess I love that this was released, it flew under my radar while I was working with the 5.10 version of the chart and Operator image. I tried to upgrade the operator image and chart from 5.10 to 5.11, but the operator did not replace the CRDs in the cluster.
In the end I had to uninstall all of my Grafana resources and have the Operator reinstall the CRDs before I could make use of the new folderRef field. Is there a better way for me to go about this in the future in case you do another update to an existing CRD(Without changing the api version)
Sadly helm does not support CRD updates. The way to upgrade CRD definitions when using helm is documented here: https://grafana.github.io/grafana-operator/docs/installation/helm/#upgrading
In short, we release CRD manifests alongside every release which you can apply directly
kubectl apply --server-side --force-conflicts -f https://github.com/grafana/grafana-operator/releases/download/v5.11.0/crds.yaml
Thank you! I was under the impression the CRDs were created by the Operator, which caused a fair amount of confusion on my end. Flux has now been updated with the relevant configs to support CRD updates https://github.com/fluxcd/flux2/issues/3953#issuecomment-1578953884
Describe the bug
Version
v5.10.0
To Reproduce Steps to reproduce the behavior:
Expected behavior All declared alerts should come into the interface.
Suspect component/Location where the bug might be occurring
unknown
Screenshots If applicable, add screenshots to help explain your problem.
Runtime (please complete the following information):