Annotations vs labels in Kubernetes - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

Purpose difference between labels and annotations

In Kubernetes, what is the main difference in purpose between labels and annotations?

A Labels are used for identifying and grouping objects; annotations store non-identifying metadata.

B Labels and annotations serve the same purpose and are interchangeable.

C Annotations are used for grouping objects; labels store large amounts of metadata.

D Annotations are only used for security settings; labels are for resource limits.

💡 Hint

Think about how Kubernetes selects objects versus storing extra info.

Labels are key-value pairs used to select and organize Kubernetes objects. Annotations store additional metadata that is not used for selection.

💻 Command Output

intermediate

Output of kubectl get with labels and annotations

Given a pod with label app=web and annotation description=frontend, what is the output of kubectl get pods --show-labels?

Kubernetes

kubectl get pods --show-labels

A

NAME   READY   STATUS   RESTARTS   AGE   LABELS
mypod   1/1     Running  0          5m    

B

NAME   READY   STATUS   RESTARTS   AGE   LABELS
mypod   1/1     Running  0          5m    description=frontend

C

NAME   READY   STATUS   RESTARTS   AGE   LABELS
mypod   1/1     Running  0          5m    app=web

D

NAME   READY   STATUS   RESTARTS   AGE   LABELS
mypod   1/1     Running  0          5m    app=web,description=frontend

💡 Hint

Labels appear with --show-labels, annotations do not.

The --show-labels flag shows only labels, not annotations.

❓ Configuration

advanced

Correct YAML snippet for adding annotation and label

Which YAML snippet correctly adds a label tier=backend and an annotation owner=teamA to a pod spec?

A

metadata:
  labels:
    tier: backend
  annotations:
    owner: teamA

B

metadata:
  annotations:
    tier: backend
  labels:
    owner: teamA

C

metadata:
  labels:
    tier: backend
  owner: teamA

D

metadata:
  labels:
    tier: backend
  annotations:
    owner

💡 Hint

Labels and annotations are separate maps under metadata.

Labels and annotations are separate keys under metadata, each with their own key-value pairs.

❓ Troubleshoot

advanced

Why does a label selector fail to find a pod?

You have a pod with annotation env=prod but no labels. You run kubectl get pods -l env=prod but get no results. Why?

A Annotations must be lowercase to match selectors.

B The pod must be restarted for labels to apply.

C Annotations are automatically converted to labels but with delay.

D Label selectors only match labels, not annotations.

💡 Hint

Think about what selectors use to find objects.

Label selectors only match labels. Annotations are ignored by selectors.

✅ Best Practice

expert

Choosing between labels and annotations for metadata

You want to store a large JSON string describing deployment details on a pod. Which is the best practice?

A Use labels because they are indexed and fast for queries.

B Use annotations because they can store large, non-identifying metadata.

C Use both labels and annotations to store the same data for redundancy.

D Store the JSON string in a ConfigMap and reference it in labels.

💡 Hint

Consider size limits and purpose of labels vs annotations.

Annotations are designed to hold large, non-identifying metadata. Labels should be small and used for selection.

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