Label selectors (equality, set-based) in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding equality-based label selectors

Which of the following label selectors will select pods with the label env exactly equal to production?

A env=production

B env in (production)

C env!=production

D env notin (production)

💡 Hint

Equality selectors use = or == to match exact label values.

The selector env=production matches pods where the label env is exactly production. Option A uses set-based syntax but is equivalent; however, the question asks specifically for equality-based selector syntax.

💻 Command Output

intermediate

Output of label selector with set-based syntax

Given the following pods with labels:

pod1: app=web, env=production
pod2: app=api, env=staging
pod3: app=web, env=staging
pod4: app=api, env=production

What pods will be selected by the label selector app in (web, api),env notin (staging)?

A pod2, pod3

B pod1, pod4

C pod1, pod2, pod3, pod4

D pod3, pod4

💡 Hint

Look for pods where app is either web or api and env is not staging.

Pods pod1 and pod4 have app label in (web, api) and env label not in (staging). Pod2 and pod3 have env=staging, so they are excluded.

❓ Configuration

advanced

Correct label selector syntax in a Deployment spec

Which of the following spec.selector.matchLabels configurations is valid for selecting pods with label tier equal to frontend?

Kubernetes

apiVersion: apps/v1
kind: Deployment
metadata:
  name: frontend-deployment
spec:
  replicas: 3
  selector:
    matchLabels:
      tier: frontend
  template:
    metadata:
      labels:
        tier: frontend
    spec:
      containers:
      - name: nginx
        image: nginx:latest

A

matchLabels:
  tier in (frontend)

B

matchLabels:
  tier == frontend

C

matchLabels:
  tier: frontend

D

matchLabels:
  tier != frontend

💡 Hint

In matchLabels, keys and values are simple key-value pairs without operators.

The matchLabels field expects a map of key-value pairs. Option C correctly uses tier: frontend. Options B, C, and D use invalid syntax for matchLabels.

❓ Troubleshoot

advanced

Troubleshooting label selector syntax error

You apply this label selector in a kubectl get pods command:

kubectl get pods -l 'env notin production'

What error will you get?

A error: invalid label selector: 'env notin production' is not a valid selector

B error: unknown flag: --notin

C No pods returned, command runs successfully

D Pods with label env=production are returned

💡 Hint

Check the syntax for set-based label selectors in kubectl commands.

The correct syntax for set-based selectors requires parentheses around the values, e.g., env notin (production). Without parentheses, the selector is invalid and causes an error.

🔀 Workflow

expert

Selecting pods with multiple label conditions

You want to select pods that have label app equal to backend and label version either v1 or v2. Which label selector will correctly select these pods?

A app in (backend),version in (v1,v2)

B app==backend,version in (v1,v2)

C app=backend,version=v1,version=v2

D app=backend,version in (v1,v2)

💡 Hint

Use equality for single value and set-based syntax for multiple values.

Option D correctly uses app=backend for exact match and version in (v1,v2) for multiple allowed values. Option D uses invalid double equals. Option D tries to assign two values to the same key, which is invalid. Option D uses set-based syntax for app which is valid but less common; however, the question asks for exact app equal to backend.

Practice

1. What does a Kubernetes label selector with environment=production do?

easy

A. Selects resources with the label key 'environment' and value 'production'.

B. Selects resources with any label key named 'production'.

C. Selects resources without the label 'environment'.

D. Selects all resources regardless of labels.

Solution

1. Step 1: Understand equality selector syntax

   The selector environment=production means the key must be 'environment' and the value must be exactly 'production'.

2. Step 2: Apply selector meaning to resource filtering

   Only resources labeled with environment=production will match this selector.

3. Final Answer:

   Selects resources with the label key 'environment' and value 'production'. -> Option A

4. Quick Check:

   Equality selector = exact key-value match [OK]

Hint: Equality selectors match exact key and value pairs [OK]

Common Mistakes:

• Confusing key and value positions
• Thinking it matches keys only
• Assuming it selects resources without the label

2. Which of the following is the correct syntax for a set-based label selector to select pods with label tier in either frontend or backend?

easy

A. tier in (frontend, backend)

B. tier = (frontend, backend)

C. tier notin (frontend, backend)

D. tier == frontend || backend

Solution

1. Step 1: Recall set-based selector syntax

   Set-based selectors use in or notin with parentheses listing values.

2. Step 2: Match syntax to requirement

   To select pods where tier is either frontend or backend, use tier in (frontend, backend).

3. Final Answer:

   tier in (frontend, backend) -> Option A

4. Quick Check:

   Set-based selector uses 'in' with parentheses [OK]

Hint: Use 'in' with parentheses for set-based inclusion [OK]

Common Mistakes:

• Using '=' instead of 'in' for sets
• Misplacing parentheses
• Using '==' or '||' which are invalid

3. Given these pods with labels:
pod1: app=web, env=prod
pod2: app=web, env=dev
pod3: app=db, env=prod
What pods will match the selector app=web,env in (prod, staging)?

medium

A. pod1 and pod2

B. pod1 only

C. pod2 only

D. pod3 only

Solution

1. Step 1: Check 'app=web' equality selector

   Pods must have label app with value web. pod1 and pod2 match this.

2. Step 2: Check 'env in (prod, staging)' set selector

   Pods must have env label with value either prod or staging. pod1 has env=prod, pod2 has env=dev.

3. Final Answer:

   pod1 only -> Option B

4. Quick Check:

   Combine equality and set selectors carefully [OK]

Hint: Check each label condition separately, then combine [OK]

Common Mistakes:

• Ignoring set-based selector values
• Selecting pods with wrong env values
• Assuming 'env=dev' matches 'env in (prod, staging)'

4. You wrote this selector to exclude pods with label env=dev: env notin (dev). But it matches pods with env=dev. What is the likely mistake?

medium

A. Using 'notin' with only one value requires no parentheses.

B. The selector should be env!=dev instead.

C. The selector syntax is correct; pods must be relabeled.

D. The label key 'env' is misspelled in some pods.

Solution

1. Step 1: Understand 'notin' selector behavior

   The selector env notin (dev) excludes pods with env=dev if the key and value match exactly.

2. Step 2: Check for label key consistency

   If pods have misspelled or missing env label, selector won't exclude them properly.

3. Final Answer:

   The label key 'env' is misspelled in some pods. -> Option D

4. Quick Check:

   Label keys must match exactly for selectors [OK]

Hint: Check label keys for typos when selectors fail [OK]

Common Mistakes:

• Assuming 'notin' works without parentheses
• Using '!=' instead of 'notin' for sets
• Ignoring label key spelling errors

5. You want to select pods that have label version set to either v1 or v2, but exclude those with label env=dev. Which selector correctly achieves this?

hard

A. version = v1 || v2, env != dev

B. version in (v1, v2) env != dev

C. version in (v1, v2), env notin (dev)

D. version in (v1, v2) && env != dev

Solution

1. Step 1: Use set-based selector for 'version'

   To select pods with version label as v1 or v2, use version in (v1, v2).

2. Step 2: Use set-based exclusion for 'env'

   To exclude pods with env=dev, use env notin (dev).

3. Step 3: Combine selectors with comma

   Separate multiple selectors with commas to combine conditions.

4. Final Answer:

   version in (v1, v2), env notin (dev) -> Option C

5. Quick Check:

   Combine set-based selectors with commas [OK]

Hint: Combine selectors with commas; use 'in' and 'notin' properly [OK]

Common Mistakes:

• Using '!=' or '||' which are invalid in selectors
• Missing commas between selectors
• Incorrect syntax for set-based selectors