Why labels organize resources in Kubernetes - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use labels in Kubernetes?

Which of the following best explains why labels are used to organize resources in Kubernetes?

A Labels encrypt resource data to secure communication between pods.

B Labels automatically create new resources based on existing ones.

C Labels allow grouping and selecting resources dynamically without changing the resource definitions.

D Labels replace the need for namespaces in Kubernetes.

💡 Hint

Think about how you find and manage groups of resources easily.

Labels are key-value pairs attached to resources. They help identify and select resources dynamically, making management easier without modifying the resources themselves.

💻 Command Output

intermediate

Output of label selection command

What is the output of the following command if two pods have the label app=frontend?

kubectl get pods -l app=frontend --no-headers -o custom-columns=NAME:.metadata.name

A

pod-frontend-1
pod-frontend-2

B No resources found.

C

NAME
pod-frontend-1
pod-frontend-2

D Error: unknown flag: --no-headers

💡 Hint

The command lists pods with a specific label and outputs only their names without headers.

The -l app=frontend filters pods with that label. The --no-headers removes the column header, and -o custom-columns=NAME:.metadata.name outputs only pod names.

❓ Configuration

advanced

Correct label selector syntax in Deployment spec

Which option shows the correct way to specify a label selector in a Kubernetes Deployment YAML to select pods with label tier: backend?

A

selector:
  labels:
    tier: backend

B

selector:
  matchLabels:
    tier: backend

C

selector:
  matchExpressions:
    - key: tier
      operator: In
      values: [backend]

D

selector:
  matchLabels:
    tier = backend

💡 Hint

Look for the standard field name used for exact label matching.

The matchLabels field is used for exact label matching with key-value pairs. The syntax must be correct YAML with colon and indentation.

❓ Troubleshoot

advanced

Why does a Service not select pods?

A Service is defined with selector app: web, but it does not route traffic to any pods. What is the most likely reason?

A Pods do not have the label <code>app: web</code> assigned.

B The Service type is set to ClusterIP instead of NodePort.

C The Service port and pod container port do not match.

D The pods are running in a different namespace than the Service.

💡 Hint

Check if the selector matches the pod labels exactly.

Services route traffic to pods matching their selector labels. If pods lack the label, the Service finds no endpoints to route to.

🔀 Workflow

expert

Label-based rolling update strategy

You want to perform a rolling update on a Deployment but only update pods with label version: v1. Which workflow step is correct to achieve this?

A Patch the Deployment selector to <code>version: v1</code> and update pod template labels to <code>version: v2</code>.

B Manually delete pods with label <code>version: v1</code>; new pods will be created with <code>version: v2</code> label.

C Create a new Deployment with label <code>version: v2</code> and delete the old Deployment with <code>version: v1</code>.

D Update the Deployment's pod template labels to <code>version: v2</code> and apply; Kubernetes will update pods matching <code>version: v1</code> to <code>v2</code> gradually.

💡 Hint

Think about how Deployment manages pods and labels during updates.

Updating the pod template labels in the Deployment triggers Kubernetes to perform a rolling update, replacing pods with old labels gradually with new ones.