What is the distinguishing feature of a Headless service in Kubernetes?

What is the distinguishing feature of a Headless service in Kubernetes?

• A. It provides a DNS implementation that routes traffic through a proxy.
• B. It uses a node port to expose each pod.
• C. It provides a DNS implementation with no proxy, so each pod handles its own traffic.
• D. It creates a single virtual IP for load balancing.

Answer: (C)

Headless services use DNS resolution without a proxy, allowing clients to connect directly to each pod. This is achieved by setting the service's cluster IP to None, so there isn’t a single virtual IP and kube-proxy doesn’t perform load balancing. Instead, DNS returns the IPs of the individual pods (and can provide SRV records as needed), enabling direct access or client-side load balancing. This is why the best description is a DNS implementation with no proxy, so each pod handles its own traffic. The other ideas describe routing through a proxy, exposing pods via NodePort, or using a single virtual IP for load balancing, which are not characteristics of headless services.

Headless services use DNS resolution without a proxy, allowing clients to connect directly to each pod. This is achieved by setting the service's cluster IP to None, so there isn’t a single virtual IP and kube-proxy doesn’t perform load balancing. Instead, DNS returns the IPs of the individual pods (and can provide SRV records as needed), enabling direct access or client-side load balancing. This is why the best description is a DNS implementation with no proxy, so each pod handles its own traffic. The other ideas describe routing through a proxy, exposing pods via NodePort, or using a single virtual IP for load balancing, which are not characteristics of headless services.