An application needs DNS that returns Pod IPs directly for custom client-side discovery instead of a single ClusterIP. Which Service configuration enables that pattern?
Select an answer to reveal the explanation.
Short Explanation
A headless Service is DNS without the virtual front desk—lookups hand you the Pod IPs so the client can pick. You get there with clusterIP: None. Handy for custom discovery; not your everyday ClusterIP load-balanced VIP.
Full Explanation
Setting spec.clusterIP: None creates a headless Service. For selector-based headless Services, DNS returns the Pod IPs (via Endpoints) rather than a single virtual ClusterIP, supporting custom discovery patterns. LoadBalancer and NodePort settings alone do not make a Service headless. A selector-less ClusterIP without clusterIP None is a different pattern (often manual Endpoints) and still not the headless DNS behavior described.