47With tens of thousands of services, DNS lookups start timing out for five seconds at a stretch. Diagnose and fix Kubernetes DNS at scale.▼hard★ EssentialNewCloudflareUberLinkedIn◆ premiumThe classic five-second stall is rarely CoreDNS being slow; it is UDP, conntrack races and ndots expansion. The diagnosis ladder and the NodeLocal DNSCache fix separate operators from readers of architecture blogs.Open full answer →
06Requests inside the cluster fail with DNS errors, but only sometimes. Diagnose it.▼hardNewUberCloudflareShopify2 repliesunlockedIntermittent DNS is the most-reported and least-understood Kubernetes failure. There are three well-known causes and each leaves a different fingerprint.Open full answer →
