fix: failed connection between grafana and alertmanager

[ferruhcihan]

📌 Summary

This PR fixes Grafana's Alertmanager datasource access by adding grafana/po-grafana to the monitoring AuthorizationPolicy. (Please check #3068)

🔍 Reviewer Notes

🧹 Checklist

• Code is readable, maintainable, and robust.
• Unit tests added/updated

[svcAPLBot]

Comparison of Helm chart templating output:

# kube-prometheus-stack/templates/extra-objects.yaml

@@ spec.rules.0.from @@
# security.istio.io/v1/AuthorizationPolicy/monitoring-auth-require-jwt
! - one list entry removed:
- - source:
-     serviceAccounts:
-     - monitoring/po-prometheus
! + one list entry added:
+ - source:
+     serviceAccounts:
+     - grafana/po-grafana
+     - monitoring/po-prometheus

# rabbitmq-cluster-operator/templates/messaging-topology-operator/validating-webhook-configuration.yaml

# values-repo.yaml

[merll]

Is this working for the team Alertmanager? Or do we need to add the exemption there as well?

[merll]

Is this working for the team Alertmanager? Or do we need to add the exemption there as well?

nvm, that should not be an issue. The Alertmanager of each team is only configured in the same team's Grafana instance. They all run in the same namespace, which already has the rules set accordingly.