Service selectors and labels in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Service Selectors in Kubernetes

What is the primary purpose of a selector in a Kubernetes Service?

A To define the network port the Service listens on

B To configure the storage volume attached to the Pods

C To assign a unique IP address to the Service

D To specify which Pods the Service should route traffic to based on matching labels

💡 Hint

Think about how a Service knows which Pods to send traffic to.

A selector in a Service matches labels on Pods to determine which Pods receive traffic. It does not configure ports, IPs, or storage.

💻 Command Output

intermediate

Output of kubectl get pods with label selector

Given the following Pods with labels:

pod1: app=web, env=prod
pod2: app=web, env=dev
pod3: app=db, env=prod

What is the output of the command kubectl get pods -l app=web,env=prod --no-headers -o custom-columns=:metadata.name?

A pod1

B pod2

C pod3

D

pod1
pod2

💡 Hint

The command filters Pods matching both labels app=web and env=prod.

Only pod1 has both labels app=web and env=prod. pod2 has env=dev, pod3 has app=db.

❓ Configuration

advanced

Correct Service selector for multiple labels

You want to create a Service that routes traffic only to Pods labeled app=frontend and tier=production. Which selector configuration is correct?

A

selector:
  app: frontend
  tier: production

B

selector:
  app: frontend,tier: production

C

selector:
  app: frontend
  tier-production: true

D

selector:
  - app=frontend
  - tier=production

💡 Hint

Selectors use key-value pairs in YAML mapping format.

The selector must be a map with keys and values. Option A correctly defines two keys with their values. Option A is invalid syntax, A uses a list which is incorrect, and D uses a wrong key name.

❓ Troubleshoot

advanced

Why does a Service not route traffic to Pods?

You created a Service with selector app: backend. However, no traffic reaches the Pods. The Pods have labels app: backend and version: v1. What is the most likely cause?

A The Service type is ClusterIP, which cannot route traffic

B The Pods are not running on the same node as the Service

C The Service selector matches the Pods, but the Pods are not ready or have no endpoints

D The Service selector does not match the Pod labels exactly due to a typo

💡 Hint

Check Pod readiness and endpoints associated with the Service.

If Pods match the selector but are not ready or have no endpoints, the Service will not route traffic. Node location does not affect routing, and ClusterIP Services route traffic inside the cluster.

🔀 Workflow

expert

Order the steps to expose a Deployment using a Service with selectors

Arrange the steps in the correct order to expose a Deployment named myapp using a Service that routes traffic to its Pods via selectors.

A 3,1,4,2

B 1,3,2,4

C 1,2,3,4

D 2,1,3,4

💡 Hint

Think about creating resources and applying them in order.

First define the Deployment with labels, then apply it. Next define the Service with matching selectors, then apply it. This ensures Pods exist before Service tries to select them.

Practice

1. What is the main purpose of a selector in a Kubernetes Service?

easy

A. To match labels on pods so the service knows which pods to send traffic to

B. To define the IP address of the service

C. To specify the container image used by pods

D. To set resource limits for pods

Solution

1. Step 1: Understand what selectors do

   A selector in a Kubernetes Service is used to find pods with matching labels.

2. Step 2: Connect selectors to pods

   The service uses the selector to route traffic only to pods that have the matching labels.

3. Final Answer:

   To match labels on pods so the service knows which pods to send traffic to -> Option A

4. Quick Check:

   Selector matches pod labels [OK]

Hint: Selector matches pod labels to connect service and pods [OK]

Common Mistakes:

• Thinking selector sets IP or image
• Confusing selector with resource limits
• Assuming selector is for service IP

2. Which of the following is the correct way to specify a selector in a Service YAML to match pods with label app: frontend?

easy

A. matchLabels:
app: frontend

B. labels:
app: frontend

C. podSelector:
app: frontend

D. selector:
app: frontend

Solution

1. Step 1: Identify correct selector syntax in Service YAML

   The Service spec uses selector: followed by key-value pairs to match pod labels.

2. Step 2: Compare options

   selector: app: frontend uses selector: with app: frontend, which is correct. Others use incorrect keys like labels, matchLabels, or podSelector which are not valid in Service spec.

3. Final Answer:

   selector: app: frontend -> Option D

4. Quick Check:

   Service selector key is 'selector' [OK]

Hint: Service selector key is always 'selector' not 'labels' or others [OK]

Common Mistakes:

• Using 'labels' instead of 'selector'
• Confusing with pod label syntax
• Using 'matchLabels' which is for label selectors, not Service

3. Given this Service selector:

selector:
  tier: backend
  env: prod

Which pods will this Service select?

medium

A. Pods with label tier=backend only

B. Pods with labels tier=backend and env=prod

C. Pods with label env=prod only

D. Pods with either tier=backend or env=prod

Solution

1. Step 1: Understand selector matching logic

   A Service selector matches pods that have all the specified labels with exact values.

2. Step 2: Apply to given selector

   The selector requires pods to have both tier=backend and env=prod labels to be selected.

3. Final Answer:

   Pods with labels tier=backend and env=prod -> Option B

4. Quick Check:

   Selector matches all labels, not any [OK]

Hint: Selector matches pods with all labels, not just one [OK]

Common Mistakes:

• Thinking selector matches pods with any one label
• Ignoring one of the labels in selector
• Confusing OR with AND logic in selectors

4. You have a Service with this selector:

selector:
  app: myapp
  version: v1

But your pods have labels:

app: myapp
version: v2

What is the problem?

medium

A. The Service selector syntax is invalid

B. The Service will select pods with version v2 anyway

C. The Service selector does not match any pods because version labels differ

D. Pods need a label 'service: myapp' to be selected

Solution

1. Step 1: Compare Service selector and pod labels

   The Service selector requires version: v1, but pods have version: v2.

2. Step 2: Understand label matching rules

   Labels must match exactly for the pod to be selected. Different version values mean no match.

3. Final Answer:

   The Service selector does not match any pods because version labels differ -> Option C

4. Quick Check:

   Exact label match required for selection [OK]

Hint: Labels must match exactly; different values mean no selection [OK]

Common Mistakes:

• Assuming partial label match works
• Thinking selector syntax is wrong
• Believing extra pod labels are needed

5. You want a Service to select pods with label app=web but exclude pods with label env=dev. How can you configure the selector?

hard

A. Use a selector with app: web and add a matchExpressions to exclude env=dev

B. Use selector:
app: web
env: !dev

C. Set selector:
app: web
env: dev

D. Label pods with app=web and remove env label from dev pods

Solution

1. Step 1: Understand label selector limitations

   Simple selectors only match labels present; to exclude labels, use matchExpressions with operators.

2. Step 2: Use matchExpressions to exclude

   You can specify matchExpressions with operator NotIn to exclude pods with env=dev.

3. Step 3: Review options

   Use a selector with app: web and add a matchExpressions to exclude env=dev correctly describes using matchExpressions to exclude labels. Use selector: app: web env: !dev syntax is invalid. Set selector: app: web env: dev includes the label to exclude. Label pods with app=web and remove env label from dev pods is about pod labeling, not selector configuration.

4. Final Answer:

   Use a selector with app: web and add a matchExpressions to exclude env=dev -> Option A

5. Quick Check:

   Exclude labels using matchExpressions NotIn [OK]

Hint: Use matchExpressions with NotIn to exclude labels in selector [OK]

Common Mistakes:

• Trying to exclude labels with simple selector syntax
• Using invalid selector syntax like env: !dev
• Confusing pod labeling with selector configuration