Label selectors (equality, set-based) in Kubernetes - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to select pods with label app equal to nginx.

Kubernetes

kubectl get pods -l app[1]nginx

Drag options to blanks, or click blank then click option'

A=

Bin

C!=

D==

Attempts:

3 left

💡 Hint

Common Mistakes

Using '==' instead of '=' causes syntax error.

Using '!=' selects pods without the label value.

Using 'in' requires a set, not a single value.

The correct syntax for equality in label selectors is =. So app=nginx selects pods with label app equal to nginx.

2fill in blank

medium

Complete the code to select pods where environment label is not production.

Kubernetes

kubectl get pods -l environment[1]production

Drag options to blanks, or click blank then click option'

A=

B!=

Cin

Dnotin

Attempts:

3 left

💡 Hint

Common Mistakes

Using '=' selects pods with the label value equal to production.

Using 'in' or 'notin' requires set syntax with parentheses.

The != operator selects pods where the label value is not equal to the given value.

3fill in blank

hard

Fix the error in the label selector to select pods with tier either frontend or backend.

Kubernetes

kubectl get pods -l tier [1] (frontend,backend)

Drag options to blanks, or click blank then click option'

Anotin

B=

C!=

Din

Attempts:

3 left

💡 Hint

Common Mistakes

Using '=' with parentheses causes syntax error.

Using '!=' or 'notin' selects pods outside the set.

The in operator is used with a set of values in parentheses to select pods with label values matching any in the set.

4fill in blank

hard

Complete the code to select pods with role label not in dev or test.

Kubernetes

kubectl get pods -l role [1] (dev,test) 

Drag options to blanks, or click blank then click option'

Anotin

Bin

C--selector

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'in' selects pods inside the set, opposite of what is needed.

Adding extra flags after the selector causes errors.

The notin operator selects pods whose label values are not in the given set. No extra flag is needed after the selector.

5fill in blank

hard

Fill both blanks to select pods with label env equal to prod and tier in frontend or backend.

Kubernetes

kubectl get pods -l env[1]prod, tier [2] (frontend,backend)

Drag options to blanks, or click blank then click option'

A=

Bin

D!=

Attempts:

3 left

💡 Hint

Common Mistakes

Using '!=' instead of '=' for equality.

Adding extra characters after the selector.

Using 'notin' instead of 'in' for tier.

Use = for equality, in for set membership, and no extra characters after the selector.

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