Library applications across many namespaces suddenly cannot resolve Service names even though the Service objects still exist. CoreDNS replicas recently crashed. What is the impact?
Select an answer to reveal the explanation.
Short Explanation
The suite doors still exist, but the directory desk is empty. If CoreDNS is down, name lookups fail even though Services and Endpoints are fine—clients that need DNS feel it immediately.
Full Explanation
Service objects and Endpoints can remain intact while CoreDNS is unavailable, yet Pods that rely on DNS names cannot resolve them. ClusterIP connectivity by literal IP may still work, but discovery by name fails cluster-wide. etcd does not serve DNS; kube-proxy does not invent NodePorts to replace DNS during a CoreDNS outage.