Building-permits workloads suddenly cannot resolve Kubernetes Service DNS names cluster-wide, and CoreDNS pods are down. How should this be classified?
Select an answer to reveal the explanation.
Short Explanation
When CoreDNS is down, it's like the city directory vanished—pods still run, but they cannot look up svc.cluster.local names. Treat it as a core component outage, not a storage quirk.
Full Explanation
CoreDNS provides in-cluster DNS for Service and pod names. If CoreDNS is unavailable, resolution fails cluster-wide and applications that depend on DNS break. Node Ready can remain true, and StorageClass problems do not by themselves disable cluster DNS. Restoring CoreDNS is the remediation path for this component class.