Adding labels to resources in Kubernetes - Step-by-Step Execution

Process Flow - Adding labels to resources

Start with resource

↓

Add label key=value

↓

Apply label to resource

↓

Verify label added

↓

Use label for selection or grouping

This flow shows how you start with a Kubernetes resource, add a label as a key=value pair, apply it, then verify and use it.

Execution Sample

Kubernetes

kubectl label pod mypod environment=production
kubectl get pod mypod --show-labels

Add a label 'environment=production' to pod 'mypod' and then show its labels.

Process Table

Step	Command	Action	Result	Output
1	kubectl label pod mypod environment=production	Add label 'environment=production' to pod 'mypod'	Label added successfully	pod/mypod labeled
2	kubectl get pod mypod --show-labels	Retrieve pod 'mypod' with labels	Labels displayed	NAME LABELS mypod environment=production
3	kubectl label pod mypod environment=production	Try adding same label again	No change, label already exists	pod/mypod labeled
4	kubectl label pod mypod tier=frontend	Add another label 'tier=frontend'	Label added successfully	pod/mypod labeled
5	kubectl get pod mypod --show-labels	Retrieve pod with updated labels	Labels displayed	NAME LABELS mypod environment=production,tier=frontend
6	kubectl get pods -l environment=production	Select pods with label environment=production	Pods filtered by label	NAME READY STATUS mypod 1/1 Running

💡 Labels added and verified; selection by label demonstrated.

Status Tracker

Variable	Start	After Step 1	After Step 4	Final
mypod.labels	none	environment=production	environment=production,tier=frontend	environment=production,tier=frontend

Key Moments - 3 Insights

Why does adding the same label twice not cause an error or change?

Because the label key=value already exists on the resource, adding it again does nothing as shown in step 3 of the execution table.

How can you check if the label was successfully added?

By running 'kubectl get pod mypod --show-labels' as in steps 2 and 5, you can see the current labels on the pod.

How do labels help in selecting resources?

Labels let you filter resources using selectors, like in step 6 where pods with 'environment=production' are listed.

Visual Quiz - 3 Questions

Look at the execution table, what labels does 'mypod' have after step 4?

A environment=production

B environment=production,tier=frontend

C tier=frontend

D none

💡 Hint

Check the 'Result' column in step 4 and the variable_tracker after step 4.

At which step do we verify the labels on 'mypod' after adding the first label?

A Step 2

B Step 3

C Step 1

D Step 6

💡 Hint

Look for the command 'kubectl get pod mypod --show-labels' in the execution_table.

If you want to select all pods with label 'environment=production', which command from the table would you use?

A kubectl label pod mypod environment=production

B kubectl get pod mypod --show-labels

C kubectl get pods -l environment=production

D kubectl label pod mypod tier=frontend

💡 Hint

Look at the 'Action' and 'Command' columns in step 6.

Concept Snapshot

Adding labels to Kubernetes resources:
- Use 'kubectl label <resource> <name> key=value' to add labels.
- Labels are key=value pairs attached to resources.
- Use 'kubectl get <resource> --show-labels' to see labels.
- Use selectors '-l key=value' to filter resources by label.
- Adding the same label twice does not change the resource.

Full Transcript

This visual execution shows how to add labels to Kubernetes resources. First, you run 'kubectl label pod mypod environment=production' to add a label. Then you verify it with 'kubectl get pod mypod --show-labels'. Adding the same label again does nothing. You can add more labels like 'tier=frontend'. Finally, you can select pods by label using 'kubectl get pods -l environment=production'. Labels help organize and select resources easily.