Organizing with recommended labels in Kubernetes - Commands & Configuration

Introduction

When you run many applications in Kubernetes, it can get hard to find and manage them. Labels help you organize and group your resources so you can easily find and control them.

When you want to group all parts of an application together for easy management.

When you need to filter and find specific resources like pods or services quickly.

When you want to apply updates or changes only to certain parts of your cluster.

When you want to track which environment (like development or production) a resource belongs to.

When you want to identify the version of an application running in your cluster.

Config File - pod.yaml

pod.yaml

apiVersion: v1
kind: Pod
metadata:
  name: example-pod
  labels:
    app.kubernetes.io/name: my-app
    app.kubernetes.io/version: "1.0"
    app.kubernetes.io/component: frontend
    app.kubernetes.io/part-of: my-application
    app.kubernetes.io/managed-by: kubectl
spec:
  containers:
  - name: nginx
    image: nginx:1.23.3
    ports:
    - containerPort: 80

This YAML file creates a Pod named example-pod with recommended labels under metadata.labels. Each label helps identify the app's name, version, component, the larger application it belongs to, and the tool managing it. These labels make it easier to organize and select resources later.

Commands

This command creates the pod with the labels defined in the YAML file. Applying the file tells Kubernetes to make this pod available in the cluster.

Terminal

kubectl apply -f pod.yaml

Expected Output

pod/example-pod created

This command lists all pods and shows their labels so you can verify the labels were applied correctly.

Terminal

kubectl get pods --show-labels

Expected Output

NAME          READY   STATUS    RESTARTS   AGE     LABELS

example-pod   1/1     Running   0          10s     app.kubernetes.io/name=my-app,app.kubernetes.io/version=1.0,app.kubernetes.io/component=frontend,app.kubernetes.io/part-of=my-application,app.kubernetes.io/managed-by=kubectl

→

--show-labels - Displays labels assigned to each pod in the list

This command filters pods to show only those with the label app.kubernetes.io/name=my-app, helping you find all pods belonging to this app.

Terminal

kubectl get pods -l app.kubernetes.io/name=my-app

Expected Output

NAME          READY   STATUS    RESTARTS   AGE

example-pod   1/1     Running   0          15s

→

-l - Filters resources by label selector

Key Concept

If you remember nothing else from this pattern, remember: labels are key-value tags that help you organize, find, and manage Kubernetes resources easily.

Common Mistakes

Using inconsistent or non-standard label keys and values.

It makes it hard to filter and group resources because labels won't match expected patterns.

Use the recommended label keys like app.kubernetes.io/name and app.kubernetes.io/version consistently.

Forgetting to apply labels in the resource YAML before creating it.

Without labels, you cannot filter or organize resources effectively later.

Always add meaningful labels under metadata.labels before applying the resource.

Using labels only on some resources but not all related ones.

This breaks grouping and makes it hard to manage the whole application as one unit.

Apply consistent labels to all related resources like pods, services, and deployments.

Summary

Create Kubernetes resources with recommended labels under metadata.labels to organize them.

Use kubectl commands with --show-labels and -l flags to view and filter resources by labels.

Consistent labeling helps manage, update, and find resources easily in your cluster.