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
Hi, I deploy External-DNS using the official helm charts. It uses the Cloudflare provider. All seems working (DNS record, controller, .... ) except retrieving metrics using the ServiceMonitor. I've got this error:
Get "http://10.0.4.199:7979/metrics": read tcp 10.0.0.129:55492->10.0.4.199:7979: read: connection reset by peer
If I try to retrieve metrics using port-forward on the Service, it works. Port-forward on the pod, it works. But if I try to retrieve metrics from other pods inside the cluster it doesn't work. wget 10.0.4.199:7979/metrics failed.
It is due to the bind address localhost in the pod and not 0.0.0.0 ... but I don't find any argument for that.
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
External-DNS version (use external-dns --version):
DNS provider:
Others:
The text was updated successfully, but these errors were encountered:
@nlamirault
I run netshoot pod in the same namespace and I'm able to access metrics:
curl http://external-dns-nonprod-external-dns:7979/metrics
# HELP external_dns_controller_last_reconcile_timestamp_seconds Timestamp of last attempted sync with the DNS provider# TYPE external_dns_controller_last_reconcile_timestamp_seconds gauge
What happened:
Hi, I deploy External-DNS using the official helm charts. It uses the Cloudflare provider. All seems working (DNS record, controller, .... ) except retrieving metrics using the ServiceMonitor. I've got this error:
If I try to retrieve metrics using port-forward on the Service, it works. Port-forward on the pod, it works. But if I try to retrieve metrics from other pods inside the cluster it doesn't work. wget 10.0.4.199:7979/metrics failed.
It is due to the bind address localhost in the pod and not 0.0.0.0 ... but I don't find any argument for that.
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
external-dns --version
):The text was updated successfully, but these errors were encountered: