Organizing with recommended labels in Kubernetes - Mini Project: Build & Apply

Organizing Kubernetes Resources with Recommended Labels

📖 Scenario: You are managing a Kubernetes cluster for a small company. To keep track of your resources easily, you want to add recommended labels to your pods. Labels help you organize and find resources quickly, like putting name tags on your belongings.

🎯 Goal: You will create a Kubernetes pod manifest with recommended labels: app.kubernetes.io/name, app.kubernetes.io/version, and app.kubernetes.io/component. Then you will verify the labels are correctly set.

📋 What You'll Learn

Create a pod manifest YAML with metadata labels

Add recommended labels exactly as specified

Use a simple pod spec with one container

Print the labels using kubectl command

💡 Why This Matters

🌍 Real World

In real Kubernetes clusters, recommended labels help teams find and manage resources easily, especially when many pods and services run together.

💼 Career

Knowing how to label Kubernetes resources is essential for DevOps roles to maintain organized, scalable, and manageable clusters.

1

Create a basic pod manifest with metadata

Create a YAML manifest for a pod named myapp-pod in the default namespace. Add the metadata section with the name set to myapp-pod. Do not add labels yet.

Kubernetes

apiVersion: v1
kind: Pod
metadata:
  name: myapp-pod
spec:
  containers:
  - name: myapp-container
    image: nginx
# Your code here

Hint

Start with the basic pod structure. Use apiVersion: v1 and kind: Pod. Add metadata with name: myapp-pod. Add a container named myapp-container using the nginx image.

2

Add recommended labels to the pod metadata

Add a labels section under metadata with these exact labels and values: - app.kubernetes.io/name: myapp - app.kubernetes.io/version: v1.0 - app.kubernetes.io/component: frontend

Kubernetes

apiVersion: v1
kind: Pod
metadata:
  name: myapp-pod
  # Add labels here
spec:
  containers:
  - name: myapp-container
    image: nginx
# Your code here

Hint

Indent the labels section under metadata. Add each label exactly as shown with correct indentation.

3

Apply the pod manifest and check labels with kubectl

Use the command kubectl apply -f pod.yaml to create the pod from your manifest file named pod.yaml. Then use kubectl get pod myapp-pod --show-labels to see the labels on the pod.

Kubernetes

# Run the commands below in your terminal
# Your code here

Hint

Make sure your manifest is saved as pod.yaml. Use kubectl apply to create or update the pod. Then check labels with kubectl get pod myapp-pod --show-labels.

4

Verify the pod labels output

Run kubectl get pod myapp-pod --show-labels and verify the output shows the labels app.kubernetes.io/name=myapp, app.kubernetes.io/version=v1.0, and app.kubernetes.io/component=frontend.

Kubernetes

# Run the command below and check output
# Your code here

Hint

The output line for myapp-pod should list all three labels exactly as shown.

Practice

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

easy

A. To encrypt data stored in Kubernetes secrets

B. To increase the CPU and memory limits of pods

C. To automatically update Kubernetes versions

D. To organize and categorize Kubernetes objects consistently

Solution

1. Step 1: Understand what labels do in Kubernetes

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

2. Step 2: Identify the role of recommended labels

   Recommended labels provide a standard way to name, version, and categorize resources for easier management.

3. Final Answer:

   To organize and categorize Kubernetes objects consistently -> Option D

4. Quick Check:

   Labels organize resources = A [OK]

Hint: Labels help group and find resources easily [OK]

Common Mistakes:

• Confusing labels with resource limits
• Thinking labels update Kubernetes versions
• Mixing labels with data encryption

2. Which of the following is the correct syntax to add a recommended label app.kubernetes.io/name: myapp to a pod YAML?

easy

A. metadata:
labels:
app.kubernetes.io/name: myapp

B. spec:
labels:
app.kubernetes.io/name: myapp

C. metadata:
annotations:
app.kubernetes.io/name: myapp

D. spec:
annotations:
app.kubernetes.io/name: myapp

Solution

1. Step 1: Identify where labels belong in Kubernetes YAML

   Labels are defined under metadata.labels in resource manifests.

2. Step 2: Check the options for correct placement

   metadata: labels: app.kubernetes.io/name: myapp correctly places the label under metadata.labels. Labels belong under metadata, not spec, and should use labels not annotations.

3. Final Answer:

   metadata: labels: app.kubernetes.io/name: myapp -> Option A

4. Quick Check:

   Labels go under metadata.labels = B [OK]

Hint: Labels always go under metadata.labels in YAML [OK]

Common Mistakes:

• Putting labels under spec instead of metadata
• Confusing labels with annotations
• Incorrect indentation in YAML

3. Given this pod YAML snippet, what label selector would match this pod?

metadata:
  labels:
    app.kubernetes.io/name: frontend
    app.kubernetes.io/version: v1

medium

A. app.kubernetes.io/name=backend

B. app.kubernetes.io/name=frontend

C. app.kubernetes.io/version=v2

D. app.kubernetes.io/component=frontend

Solution

1. Step 1: Read the pod's labels

   The pod has labels app.kubernetes.io/name: frontend and app.kubernetes.io/version: v1.

2. Step 2: Match the selector to the labels

   Only app.kubernetes.io/name=frontend matches the label key and value exactly. The other options use mismatched keys or values.

3. Final Answer:

   app.kubernetes.io/name=frontend -> Option B

4. Quick Check:

   Selector matches label key and value = C [OK]

Hint: Selector must exactly match label key and value [OK]

Common Mistakes:

• Using wrong label values
• Confusing label keys
• Using non-existent labels in selector

4. You applied this YAML but your pod is not selected by the service selector:

metadata:
  labels:
    app.kubernetes.io/name: frontend
spec:
  containers:
  - name: app
    image: nginx

What is the likely problem?

medium

A. The service selector does not match the pod labels

B. Labels are under spec instead of metadata

C. The container image is incorrect

D. The label key is missing the recommended prefix

Solution

1. Step 1: Check the pod labels

   The pod has label app.kubernetes.io/name: frontend under metadata.labels, which is correct.

2. Step 2: Understand why the service selector might fail

   If the service selector does not exactly match the pod's labels, the pod won't be selected. The problem is likely a mismatch in the service selector, not the pod labels or container image.

3. Final Answer:

   The service selector does not match the pod labels -> Option A

4. Quick Check:

   Selector must match pod labels = D [OK]

Hint: Service selector must exactly match pod labels [OK]

Common Mistakes:

• Assuming label keys are incorrect when they are correct
• Thinking labels belong under spec
• Blaming container image for selector issues

5. You want to organize your Kubernetes resources using recommended labels for app name, version, and component. Which set of labels should you apply to a backend service named api version v2?

hard

A. app: api
ver: v2
comp: backend

B. name: api
version: v2
component: backend

C. app.kubernetes.io/name: api
app.kubernetes.io/version: v2
app.kubernetes.io/component: backend

D. app.kubernetes.io/name: api
app.kubernetes.io/version: v1
app.kubernetes.io/component: backend

Solution

1. Step 1: Identify the recommended label keys

   Recommended labels use the prefix app.kubernetes.io/ followed by keys like name, version, and component.

2. Step 2: Match the correct values for the backend service

   The service is named api, version v2, and component backend. app.kubernetes.io/name: api app.kubernetes.io/version: v2 app.kubernetes.io/component: backend correctly uses recommended keys and values. Other options either lack the app.kubernetes.io/ prefix or use the wrong version (v1).

3. Final Answer:

   app.kubernetes.io/name: api app.kubernetes.io/version: v2 app.kubernetes.io/component: backend -> Option C

4. Quick Check:

   Use recommended keys with correct values = A [OK]

Hint: Use full recommended label keys with correct values [OK]

Common Mistakes:

• Using short or incorrect label keys
• Applying wrong version value
• Omitting the recommended prefix