Annotations vs labels in Kubernetes - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to add a label named env with value production to the pod metadata.

Kubernetes

metadata:
  labels:
    env: [1]

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

Aproduction

Bdev

Ctest

Dstaging

Attempts:

3 left

💡 Hint

Common Mistakes

Using annotations syntax instead of labels

Misspelling the key or value

The label env is set to production to mark the pod environment.

2fill in blank

medium

Complete the code to add an annotation named description with value frontend pod to the pod metadata.

Kubernetes

metadata:
  annotations:
    description: [1]

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

Abackend pod

Bdatabase pod

Cfrontend pod

Dcache pod

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing annotations with labels

Using label syntax for annotations

Annotations store non-identifying metadata like descriptions. Here, it describes the pod as 'frontend pod'.

3fill in blank

hard

Fix the error in the label selector to select pods with label tier equal to frontend.

Kubernetes

kubectl get pods -l tier=[1]

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

Afront-end

Bfrontend

Cfront_end

Dfront end

Attempts:

3 left

💡 Hint

Common Mistakes

Using spaces or underscores instead of exact label value

Incorrect casing

The label value must exactly match the label assigned to pods. Here, it is 'frontend'.

4fill in blank

hard

Fill both blanks to create a pod manifest with a label app set to nginx and an annotation maintainer set to team-a.

Kubernetes

metadata:
  labels:
    app: [1]
  annotations:
    maintainer: [2]

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

Anginx

Bteam-b

Cteam-a

Dapache

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping label and annotation values

Using wrong team names

The label app is set to 'nginx' to identify the application. The annotation maintainer is set to 'team-a' to indicate ownership.

5fill in blank

hard

Fill all three blanks to create a pod manifest with label role set to db, annotation backup set to daily, and label zone set to us-east.

Kubernetes

metadata:
  labels:
    role: [1]
    zone: [2]
  annotations:
    backup: [3]

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

Aweekly

Bus-east

Cdaily

Ddb

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing labels and annotations

Using wrong backup frequency

The label role is 'db' to indicate database pods. The label zone is 'us-east' for location. The annotation backup is 'daily' to specify backup frequency.

Practice

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

easy

A. To group and select objects for operations like deployments and services

B. To store large binary data inside objects

C. To provide detailed descriptions for human readers only

D. To encrypt sensitive information within the cluster

Solution

1. Step 1: Understand labels' role

   Labels are key-value pairs used to organize and select Kubernetes objects for management tasks.

2. Step 2: Differentiate from annotations

   Annotations store metadata but are not used for selecting or grouping objects.

3. Final Answer:

   To group and select objects for operations like deployments and services -> Option A

4. Quick Check:

   Labels = grouping and selection [OK]

Hint: Labels are for grouping; annotations are for extra info [OK]

Common Mistakes:

• Confusing annotations as selectors
• Thinking labels store large data
• Assuming labels encrypt data

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

easy

A. metadata:
annotations:
env: production

B. spec:
labels:
env: production

C. metadata:
labels:
- env=production

D. metadata:
labels:
env: production

Solution

1. Step 1: Locate correct YAML section

   Labels belong under metadata.labels in Kubernetes YAML.

2. Step 2: Check syntax format

   Labels are key-value pairs, not lists or under spec.

3. Final Answer:

   metadata: labels: env: production -> Option D

4. Quick Check:

   Labels under metadata.labels with key: value [OK]

Hint: Labels go under metadata.labels as key-value pairs [OK]

Common Mistakes:

• Putting labels under spec section
• Using annotations instead of labels
• Writing labels as a list instead of map

3. Given this pod YAML snippet, what will kubectl get pods -l app=web return?

metadata:
  labels:
    app: web
  annotations:
    description: "Frontend web server"

medium

A. The command will fail due to syntax error

B. The pod will not be listed because annotations are ignored

C. The pod will be listed because it has label app=web

D. The pod will be listed only if annotation description exists

Solution

1. Step 1: Understand label selector behavior

   The command kubectl get pods -l app=web lists pods with label app=web.

2. Step 2: Check pod labels and annotations

   The pod has label app: web, so it matches the selector. Annotations do not affect selection.

3. Final Answer:

   The pod will be listed because it has label app=web -> Option C

4. Quick Check:

   Label selector matches label, annotations ignored [OK]

Hint: Label selectors ignore annotations, only match labels [OK]

Common Mistakes:

• Thinking annotations affect label selectors
• Assuming command fails due to annotations
• Confusing labels and annotations roles

4. You want to add extra metadata to a deployment without affecting its selection. Which is the correct fix if you mistakenly added this under metadata.labels instead of metadata.annotations?

metadata:
  labels:
    description: "Handles user login"

medium

A. Move the key-value pair under metadata.annotations instead of labels

B. Keep it under labels but rename key to 'desc'

C. Remove the key-value pair entirely

D. Add the key-value pair under spec.containers

Solution

1. Step 1: Identify misuse of labels

   Labels affect selection and grouping; adding descriptive info there can cause unintended behavior.

2. Step 2: Correct placement for metadata

   Annotations are meant for extra metadata that does not affect selection, so move the key-value pair there.

3. Final Answer:

   Move the key-value pair under metadata.annotations instead of labels -> Option A

4. Quick Check:

   Metadata info belongs in annotations, not labels [OK]

Hint: Put extra info in annotations, not labels [OK]

Common Mistakes:

• Using labels for descriptive metadata
• Renaming keys instead of moving
• Removing useful metadata

5. You have a service that selects pods with label tier=backend. You want to add a note about the pod's version without affecting service selection. Which YAML snippet correctly applies this?

hard

A. metadata:
labels:
tier: backend
version: "v2.1"

B. metadata:
labels:
tier: backend
annotations:
version: "v2.1"

C. metadata:
annotations:
tier: backend
version: "v2.1"

D. spec:
labels:
tier: backend
annotations:
version: "v2.1"

Solution

1. Step 1: Identify label for selection

   The service selects pods with label tier=backend, so this label must be present under metadata.labels.

2. Step 2: Add version note without affecting selection

   Version info is metadata and should go under metadata.annotations to avoid changing label selectors.

3. Final Answer:

   metadata: labels: tier: backend annotations: version: "v2.1" -> Option B

4. Quick Check:

   Labels for selection, annotations for extra info [OK]

Hint: Keep selectors in labels; notes in annotations [OK]

Common Mistakes:

• Putting version as label and changing selectors
• Putting tier in annotations losing selection
• Placing labels or annotations under spec