An open-data portal needs DNS that returns Pod IPs for a discovery pattern similar to StatefulSet peers, not a single load-balanced ClusterIP. Which Service configuration produces that DNS behavior?
Select an answer to reveal the explanation.
Short Explanation
A normal ClusterIP Service is like a single front desk number that hides who is in the back. A headless Service (clusterIP: None) throws away that shared number and lets DNS hand out the actual desk phone numbers—the Pod IPs. That’s what you want for peer discovery patterns, including many StatefulSet-style setups.
Full Explanation
Headless Services set spec.clusterIP to None. Without a virtual ClusterIP, CoreDNS returns A/AAAA records for the Pods selected by the Service (and for StatefulSets, stable per-pod DNS names under the governing Service). A standard ClusterIP Service instead returns the Service IP for load-balanced access. LoadBalancer, ExternalName, and dnsPolicy annotations do not provide headless Pod-IP discovery semantics.