Headless services concept in Kubernetes - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a headless service in Kubernetes?

A headless service is a Kubernetes service without a cluster IP. It allows direct access to the individual pods instead of load balancing through a single IP.

beginner

How does a headless service differ from a normal Kubernetes service?

A normal service has a cluster IP that load balances traffic to pods. A headless service has no cluster IP and returns pod IPs directly for client-side load balancing.

intermediate

Why use a headless service in Kubernetes?

Use headless services when you want clients to connect directly to pods, for example, in stateful applications or when you need custom load balancing.

intermediate

What DNS behavior does a headless service provide?

A headless service returns multiple A records with the IPs of all pods matching the service selector, enabling clients to discover all pod IPs.

beginner

How do you define a headless service in a Kubernetes YAML file?

Set the service spec field 'clusterIP' to 'None' to make the service headless.

What value should 'clusterIP' have to create a headless service?

A "" (empty string)

B "0.0.0.0"

C "127.0.0.1"

D "None"

Setting 'clusterIP' to 'None' disables the cluster IP and makes the service headless.

What does a headless service return when queried via DNS?

A Single cluster IP address

B External IP address

C IP addresses of all pods matching the selector

D No IP addresses

Headless services return multiple pod IPs for client-side load balancing.

Which scenario is best suited for using a headless service?

A Stateful applications needing direct pod access

B Stateless apps needing simple load balancing

C Exposing services outside the cluster

D Assigning external IPs

Stateful apps often require direct pod connections, which headless services enable.

What happens if you omit 'clusterIP' in a service spec?

A Service is invalid and won't create

B Kubernetes assigns a cluster IP automatically

C Service becomes headless

D Service gets an external IP

By default, Kubernetes assigns a cluster IP if 'clusterIP' is not set.

How do clients perform load balancing with headless services?

A Clients use DNS to get all pod IPs and balance themselves

B Kubernetes load balances automatically

C Clients connect to a single cluster IP

D Load balancing is not possible

Clients receive all pod IPs and decide how to distribute traffic.

Explain what a headless service is and why you might use one in Kubernetes.

Think about how traffic reaches pods differently than normal services.

Describe how DNS works with a headless service in Kubernetes.

Focus on what happens when you look up the service name.

Practice

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

easy

A. To connect directly to pods without using a load balancer

B. To expose a service externally via a cloud provider

C. To automatically scale pods based on traffic

D. To create a persistent volume for storage

Solution

1. Step 1: Understand service types in Kubernetes

   Regular services use a load balancer or cluster IP to route traffic to pods.

2. Step 2: Identify the role of headless services

   Headless services remove the cluster IP, allowing direct pod connections without load balancing.

3. Final Answer:

   To connect directly to pods without using a load balancer -> Option A

4. Quick Check:

   Headless service = direct pod connection [OK]

Hint: Headless means no cluster IP, direct pod access [OK]

Common Mistakes:

• Confusing headless service with external load balancer
• Thinking headless services scale pods automatically
• Assuming headless services provide storage

2. Which YAML field must be set to create a headless service in Kubernetes?

easy

A. type: Headless

B. externalTrafficPolicy: Local

C. clusterIP: None

D. loadBalancerIP: 0.0.0.0

Solution

1. Step 1: Recall the service spec for headless services

   Headless services are defined by setting clusterIP to None in the service spec.

2. Step 2: Check other options for correctness

   type: Headless is invalid; loadBalancerIP and externalTrafficPolicy relate to load balancers, not headless services.

3. Final Answer:

   clusterIP: None -> Option C

4. Quick Check:

   clusterIP None = headless service [OK]

Hint: Set clusterIP to None for headless service [OK]

Common Mistakes:

• Using type: Headless instead of clusterIP: None
• Confusing loadBalancerIP with clusterIP
• Setting externalTrafficPolicy for headless service

3. Given this service YAML snippet, what will be the DNS behavior?

apiVersion: v1
kind: Service
metadata:
  name: my-headless-service
spec:
  clusterIP: None
  selector:
    app: myapp
  ports:
  - port: 80
    targetPort: 8080

medium

A. DNS returns multiple pod IPs matching the selector

B. DNS returns a single IP of a load balancer

C. DNS returns no IP because clusterIP is None

D. DNS returns the external IP of the cluster

Solution

1. Step 1: Analyze clusterIP: None effect on DNS

   With clusterIP set to None, DNS returns the IPs of all pods matching the selector, not a single IP.

2. Step 2: Understand DNS response for headless services

   DNS returns multiple A records, one per pod IP, enabling direct pod access.

3. Final Answer:

   DNS returns multiple pod IPs matching the selector -> Option A

4. Quick Check:

   Headless DNS = multiple pod IPs [OK]

Hint: Headless service DNS returns pod IPs, not one IP [OK]

Common Mistakes:

• Thinking DNS returns a load balancer IP
• Assuming no IP is returned when clusterIP is None
• Confusing external IP with pod IPs

4. You created a headless service but your pods are not reachable via DNS. What is a likely cause?

medium

A. You forgot to set clusterIP: None in the service spec

B. Your pods do not have matching labels for the service selector

C. You used type: LoadBalancer instead of clusterIP: None

D. You exposed the service with NodePort instead of ClusterIP

Solution

1. Step 1: Check service selector and pod labels

   If pods do not match the service selector labels, the service cannot route traffic to them.

2. Step 2: Verify clusterIP and service type correctness

   clusterIP: None is required for headless service; type LoadBalancer or NodePort changes service behavior but won't cause DNS pod reachability issues if labels match.

3. Final Answer:

   Your pods do not have matching labels for the service selector -> Option B

4. Quick Check:

   Selector mismatch = pods unreachable [OK]

Hint: Check pod labels match service selector [OK]

Common Mistakes:

• Ignoring pod labels and selector mismatch
• Confusing service type with label issues
• Assuming NodePort affects headless DNS reachability

5. You want to deploy a stateful app that requires direct pod access and custom load balancing. Which Kubernetes service setup is best?

hard

A. Create a ClusterIP service with externalTrafficPolicy set to Local

B. Use a LoadBalancer service with multiple replicas

C. Use a NodePort service with a Deployment

D. Create a headless service with clusterIP: None and use StatefulSet pods

Solution

1. Step 1: Understand requirements for stateful apps

   Stateful apps often need stable network IDs and direct pod access for custom load balancing.

2. Step 2: Match Kubernetes service type to requirements

   Headless services (clusterIP: None) combined with StatefulSets provide stable pod identities and direct access.

3. Step 3: Evaluate other options

   LoadBalancer and NodePort services use load balancing and do not provide stable pod DNS; ClusterIP with externalTrafficPolicy affects routing but not pod identity.

4. Final Answer:

   Create a headless service with clusterIP: None and use StatefulSet pods -> Option D

5. Quick Check:

   Stateful + headless + StatefulSet = best fit [OK]

Hint: StatefulSet + headless service = stable pod access [OK]

Common Mistakes:

• Using LoadBalancer for stateful direct pod access
• Confusing NodePort with headless service benefits
• Ignoring StatefulSet for stable pod identities