Headless services concept in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the main purpose of a headless service in Kubernetes?

In Kubernetes, a headless service is different from a normal service. What is its main purpose?

A To provide a stable IP address for pods behind the service

B To allow direct access to individual pods without load balancing

C To automatically scale pods based on traffic

D To expose the service externally via a cloud provider load balancer

💡 Hint

Think about how headless services handle DNS and pod access.

A headless service does not assign a cluster IP. Instead, it returns the IPs of the pods directly, allowing clients to connect to individual pods without load balancing.

💻 Command Output

intermediate

What is the output of this command for a headless service?

Given a headless service named my-service in namespace default, what will the following command output?

kubectl get svc my-service -o jsonpath='{.spec.clusterIP}'

A None

B 10.96.0.1

C Headless

D None or "" (empty string)

💡 Hint

Check what the clusterIP field is set to for headless services.

For headless services, the clusterIP field is set to None (as a string), indicating no cluster IP is assigned.

❓ Configuration

advanced

Which YAML snippet correctly defines a headless service?

Choose the YAML snippet that correctly creates a headless service named db-service targeting pods with label app: database.

A

apiVersion: v1
kind: Service
metadata:
  name: db-service
spec:
  clusterIP: 0.0.0.0
  selector:
    app: database
  ports:
  - port: 5432
    targetPort: 5432

B

apiVersion: v1
kind: Service
metadata:
  name: db-service
spec:
  clusterIP: 10.0.0.1
  selector:
    app: database
  ports:
  - port: 5432
    targetPort: 5432

C

apiVersion: v1
kind: Service
metadata:
  name: db-service
spec:
  type: LoadBalancer
  selector:
    app: database
  ports:
  - port: 5432
    targetPort: 5432

D

apiVersion: v1
kind: Service
metadata:
  name: db-service
spec:
  clusterIP: None
  selector:
    app: database
  ports:
  - port: 5432
    targetPort: 5432

💡 Hint

Remember how to disable cluster IP assignment for headless services.

Setting clusterIP: None in the service spec creates a headless service. Other values assign a cluster IP or specify a load balancer.

❓ Troubleshoot

advanced

Why might a client fail to resolve pod IPs from a headless service DNS name?

You created a headless service, but clients cannot resolve the pod IPs using the service DNS name. What is a likely cause?

A The service selector labels do not match any pods

B The service has a cluster IP assigned

C The pods are not exposing any ports

D The service type is set to LoadBalancer

💡 Hint

Check if the service can find pods to route to.

If the service selector does not match any pods, DNS queries for the headless service return no pod IPs, causing resolution failure.

✅ Best Practice

expert

What is the recommended use case for headless services in Kubernetes?

Among these options, which best describes when to use a headless service?

A When exposing a service externally to the internet via cloud load balancer

B When you want to load balance traffic evenly across pods automatically

C When you need to discover and connect to individual pods directly, such as for stateful applications

D When you want to assign a fixed IP address to a service

💡 Hint

Think about applications that require direct pod connections.

Headless services are ideal for stateful apps or when clients need to connect to specific pods directly, bypassing load balancing.