Why labels organize resources in Kubernetes - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to add a label to a Kubernetes pod.

Kubernetes

kubectl label pods my-pod environment=production [1]

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

A--overwrite

B--selector

C--all

D--dry-run

Attempts:

3 left

💡 Hint

Common Mistakes

Using --selector instead of --overwrite

Forgetting to add the flag causes error if label exists

The --overwrite flag allows updating an existing label on the pod.

2fill in blank

medium

Complete the command to list pods with the label app=frontend.

Kubernetes

kubectl get pods -l [1]

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

Atier=database

Bapp=backend

Capp=frontend

Denvironment=production

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong label key or value

Omitting the -l flag

The -l flag filters pods by label. Here, we want pods labeled app=frontend.

3fill in blank

hard

Fix the error in the command to delete pods with label tier=backend.

Kubernetes

kubectl delete pods -l [1]

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

Atier=frontend

Btier=backend

Capp=backend

Denvironment=staging

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong label value

Deleting pods without label filter

The command deletes pods with label tier=backend. Using the correct label ensures the right pods are deleted.

4fill in blank

hard

Fill both blanks to create a label selector for pods with app=web and environment=prod.

Kubernetes

kubectl get pods -l [1],[2]

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

Aapp=web

Bapp=api

Cenvironment=prod

Denvironment=dev

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong label keys or values

Adding spaces after commas

Multiple labels can be combined with commas. Here, app=web and environment=prod select pods matching both labels.

5fill in blank

hard

Fill all three blanks to create a dictionary of labels in a pod YAML manifest.

Kubernetes

metadata:
  labels:
    [1]: [2]
    [3]: production

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

Aapp

Bfrontend

Cenvironment

Dbackend

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping keys and values

Using incorrect label names

Labels in YAML are key-value pairs. Here, app: frontend and environment: production label the pod correctly.

Practice

1. What is the main purpose of labels in Kubernetes?

easy

A. To organize and group resources for easy management

B. To store large amounts of data inside pods

C. To define network policies between nodes

D. To control user access permissions

Solution

1. Step 1: Understand what labels do

   Labels are tags attached to Kubernetes objects to identify and group them.

2. Step 2: Identify the main use

   Labels help select and organize resources, making management easier.

3. Final Answer:

   To organize and group resources for easy management -> Option A

4. Quick Check:

   Labels = Organize resources [OK]

Hint: Labels tag resources to group and manage them easily [OK]

Common Mistakes:

• Confusing labels with data storage
• Thinking labels control network or permissions
• Mixing labels with annotations

2. Which of the following is the correct syntax to add a label env=production to a pod using kubectl?

easy

A. kubectl label pod mypod env=production

B. kubectl add label pod mypod env=production

C. kubectl set label pod mypod env=production

D. kubectl apply label pod mypod env=production

Solution

1. Step 1: Recall kubectl label command

   The correct command to add or update a label is kubectl label.

2. Step 2: Check syntax correctness

   kubectl label pod mypod env=production uses kubectl label pod mypod env=production, which is correct syntax.

3. Final Answer:

   kubectl label pod mypod env=production -> Option A

4. Quick Check:

   Use kubectl label to add labels [OK]

Hint: Use 'kubectl label' to add or change labels [OK]

Common Mistakes:

• Using 'kubectl add label' which is invalid
• Confusing 'set label' with 'label'
• Using 'apply label' which does not exist

3. Given these pods with labels:
pod1: app=web, env=prod
pod2: app=web, env=dev
pod3: app=db, env=prod
What pods will be selected by the command kubectl get pods -l app=web,env=prod?

medium

A. pod1 and pod2

B. pod1 only

C. pod2 only

D. pod3 only

Solution

1. Step 1: Understand label selector syntax

   The selector app=web,env=prod means pods must have both labels with these exact values.

2. Step 2: Match pods with labels

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

3. Final Answer:

   pod1 only -> Option B

4. Quick Check:

   Selector matches pod1 only [OK]

Hint: Selector with commas means AND condition [OK]

Common Mistakes:

• Assuming comma means OR instead of AND
• Ignoring one label in selector
• Confusing label keys and values

4. You tried to select pods with kubectl get pods -l app:web but got an error. What is wrong with this command?

medium

A. Labels cannot be used with 'kubectl get pods'

B. The pod name is missing

C. The label selector syntax uses '=' not ':'

D. The command needs '--all-namespaces' flag

Solution

1. Step 1: Check label selector syntax

   Kubernetes label selectors use '=' to assign values, not ':'.

2. Step 2: Identify error cause

   Using ':' causes syntax error, so command fails.

3. Final Answer:

   The label selector syntax uses '=' not ':' -> Option C

4. Quick Check:

   Use '=' in label selectors [OK]

Hint: Label selectors use '=' not ':' [OK]

Common Mistakes:

• Using ':' instead of '=' in selectors
• Forgetting pod name is not needed with -l
• Thinking labels can't filter pods

5. You want to deploy two versions of the same app in Kubernetes: v1 and v2. How can labels help you manage these versions efficiently?

hard

A. Labels automatically update pods to the latest version

B. Use labels to store the entire app code inside pods

C. Labels prevent pods from communicating with each other

D. Assign labels like version=v1 and version=v2 to pods and use selectors to target them

Solution

1. Step 1: Understand version management with labels

   Labels can tag pods with version info like version=v1 or version=v2.

2. Step 2: Use selectors to manage versions

   You can select and manage pods by version using label selectors in commands or deployments.

3. Final Answer:

   Assign labels like version=v1 and version=v2 to pods and use selectors to target them -> Option D

4. Quick Check:

   Labels separate versions for easy management [OK]

Hint: Label versions to select and manage app updates easily [OK]

Common Mistakes:

• Thinking labels store app code
• Assuming labels auto-update pods
• Believing labels block pod communication