access to prometheus datasource from grafana

[p1-repo-sync-bot[bot]]

Bug

Description

new authorization polices in 2.23.1 prevent access to datesource from grafana , grafana lives in a separate cluster monitoring kiali-prometheus-authz-policy
monitoring monitoring-prometheus-authz-policy
monitoring prometheus-am

Provide any steps possible used to reproduce the error (ideally in an isolated fashion). removing the auth policies fixes the issue

BigBang Version

upgrading from 2.22.0 to 2.23.1

What version of BigBang were you running? 2.22.0 This can be retrieved multiple ways:

# via helm
helm ls -n bigbang

# via the deployed umbrella git tag
kubectl get gitrepository -n bigbang

[p1-repo-sync-bot[bot]]

jimmyungerman commented:

---

Hi @carl5184. Do you mind sharing more about your setup? Are both clusters running bigbang with Istio Service Mesh?

[p1-repo-sync-bot[bot]]

carl5184 commented:

---

Yes, both are big bang, but the one with grafana isn't being upgraded at the moment, the 3 authorization polices are preventing the datasource in grafana from working

[p1-repo-sync-bot[bot]]

jimmyungerman commented:

---

Just to make sure I have all the details to research this a bit:

• 1 bigbang cluster with grafana that has no authorization policies in it
• 1 bigbang cluster with prometheus in it that contains the 3 authorization policies that are currently blocking traffic?

[p1-repo-sync-bot[bot]]

carl5184 commented:

---

Jimmy, looks like they fixed it in 2.25.0 by adding this to the auth policy ".Values.sso.enabled"

you can close the ticket , thank you

[p1-repo-sync-bot[bot]]

Issue 'access to prometheus datasource from grafana' closed from GitLab side

[p1-repo-sync-bot[bot]]

jimmyungerman commented:

---

Thanks for the update @carl5184 !