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
I would expect the charm to pass through the ingress IP (or possibly the service ClusterIP?) as the defined target instead - these are in the 10.0.0.0/8 range rather than 192.168.0.0/16.
To Reproduce
Deploy and expose httprequest-lego-provider via nginx-ingress-integrator.
Integrate the service with COS.
Failure to scrape metrics target.
Environment
Deployed on a shared Kubernetes cluster on Openstack.
Relevant log output
Nothing obviously relevant on this side, but feel free to request specific logs.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Bug Description
Hi,
We've got this deployed and related/integrated with COS, but are seeing an error due to COS's inability to scrape the defined Prometheus target.
On closer investigation, the source of the error is an inability to scrape the actual pod IP, rather than the service/ingress IP.
The configured target is http://192.168.102.222:9102/metrics
I would expect the charm to pass through the ingress IP (or possibly the service ClusterIP?) as the defined target instead - these are in the 10.0.0.0/8 range rather than 192.168.0.0/16.
To Reproduce
Deploy and expose httprequest-lego-provider via nginx-ingress-integrator.
Integrate the service with COS.
Failure to scrape metrics target.
Environment
Deployed on a shared Kubernetes cluster on Openstack.
Relevant log output
Additional context
No response
The text was updated successfully, but these errors were encountered: