Then this probably isn't an alertmanager problem, it's a kubernetes problem.
Are you running dual-stack Kubernetes? This is an alpha feature (which means it's behind a feature gate): https://kubernetes.io/docs/concepts/services-networking/dual-stack/ I haven't tried it. What I did find in a normal cluster is, when you bind to a port, k8s does bind() and listen() for the port on both protocols. It then configures iptables traffic forwarding for IPv4 only. This means the IPv6 address will establish a connection and block. This is particularly painful for services bound to localhost, because typically /etc/hosts maps localhost to both ::1 and 127.0.0.1. The client tries to connect to ::1, establishes a TCP connection, and then nothing happens :-( Anyway, the problem seems most likely to do with kubernetes, so probably ought to move to a k8s forum. You can use your browser console logs, and/or tcpdump, to isolate where the problem is. -- You received this message because you are subscribed to the Google Groups "Prometheus Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/3beddbb4-701d-409e-b954-ef7b2a7d3f48o%40googlegroups.com.
