You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But the service monitor wasn't able to fetch the metrics as it wasn't able to connect to the grafana-image-renderer pod with the TPC error connection refused.
It appears that the issue is caused by the configured image-renderer-ingress network policy that only allow connection from the grafana pod.
What I would expect is that when the service monitor is enabled that the ingress is configured to allow prometheus to scrap the metrics from the image-renderer pod.
Workaround
Currently, I have a workaround that use the extraIngressSelectors to select the prometheus pod.
The text was updated successfully, but these errors were encountered:
FirelightFlagboy
changed the title
[grafana] [image-renderer] Service monitor because the ingress network policy does not allow prometheus to connect
[grafana] [image-renderer] Service monitor not working because the ingress network policy does not allow prometheus to connect
Aug 10, 2024
Hello, I have configured the
grafana-image-renderer
with thegrafana/grafana
helm with the following configuration:But the service monitor wasn't able to fetch the metrics as it wasn't able to connect to the
grafana-image-renderer
pod with the TPC errorconnection refused
.It appears that the issue is caused by the configured
image-renderer-ingress
network policy that only allow connection from thegrafana
pod.What I would expect is that when the service monitor is enabled that the ingress is configured to allow prometheus to scrap the metrics from the
image-renderer
pod.Workaround
Currently, I have a workaround that use the
extraIngressSelectors
to select the prometheus pod.The text was updated successfully, but these errors were encountered: