3 ms·

This assumes it's not a DNS problem, and it's ALWAYS DNS.

• hinkley 5y ago
  Is that why consul has dns built into it?
  • sascha_sl 5y ago
    The point isn't that DNS is bad, but it is often neglected as a problem source, something taken a bit too much for granted. The Kubernetes community loves this saying because pairing something like nodejs (which doesn't do DNS caching) with a Docker image with no local DNS cache/resolver and a Kubernetes cluster that doesn't usually come with a highly scaled DNS server out of the box often leads to DNS failing more often than anticipated. Also kube-dns, the now deprecated default DNS, was extremely shit. I have a pcap file captured on a kubernetes node with 60000 DNS packets in a 0.2s frame. They're all queries for s3.amazonaws.com.