The sanitation platform team asks which object supplies the stable ClusterIP that application Pods use as their nameserver for cluster DNS. What is the correct answer?
Select an answer to reveal the explanation.
Short Explanation
Apps don’t memorize every CoreDNS Pod’s personal cell number—they dial one stable front-desk line. That line is the cluster DNS Service (often still named kube-dns) whose selector points at CoreDNS Pods. The ClusterIP stays put while Pods churn behind it.
Full Explanation
Cluster DNS is exposed to Pods as a Service ClusterIP—historically and commonly named kube-dns—even when the implementation Pods are CoreDNS. Kubelet injects that Service IP into Pod resolv.conf (unless overridden). Relying on individual Pod IPs, treating kubelet hostname alone as cluster DNS, or confusing Ingress with DNS are incorrect models of how Kubernetes name resolution is fronted.