[Bug] GrafanaAlertRuleGroup changes when applied about grafana-operator

[theSuess]

I see. I don't think there's anything we can do about this from an operator perspective (as the data representation is handled differently in k8s vs Grafana).

I'll close this issue and check with the alerting team to see if we can add a separate export format for an operator compatible CR into Grafana

[pb82]

@AlexEndris it sounds like the Operator removes fields that are not in the spec and then ArgoCD applies them again. In that case, wouldn't it make sense to remove those fields (and use the 5m0s format for the other)?

[AlexEndris]

@pb82 Thank you for your reply. My point was that the yaml is just a copy & paste from what grafana itself exports in version 10.4.1. I assumed that those would be the same.

[theSuess]

The duration fields in the Kubernetes custom resource are using a different duration type than the Grafana export, that's why the saved resource shows a different to the Grafana export.

Does this cause any problems or is it just a cosmetic issue?

[AlexEndris]

@theSuess It actually causes ArgoCD to detect a difference and tries to constantly sync the state, overwriting the manifest over and over. We had to adjust the export manually to stop this.

[AlexEndris]

@theSuess Thank you for the consideration! That would definitely help reducing manually having to change this. ❤️

[dcharbonnier]

until this is solved I did this:

 grafana.integreatly.org/GrafanaAlertRuleGroup:
      ignoreDifferences: |
        jqPathExpressions:
        - .spec.rules[].data[].relativeTimeRange
        - .spec.rules[].isPaused

a very bad solution but this issue create too much load on argocd