DevOps Glossary

Kubernetes Labels and Selectors are the metadata tags and matching rules Kubernetes uses to organize, find, and target objects. A label is a key-value pair, such as app=api, env=prod, or tier=backend, attached to resources like Pods, Services, Deployments, Nodes, and PersistentVolumes. A selector matches those labels so Kubernetes can group the right objects for a Service, Deployment, ReplicaSet, NetworkPolicy, scheduling rule, or kubectl command. For example, a Service with the selector app=payments routes traffic only to Pods carrying that label. Labels are flexible and support operational patterns such as separating dev, staging, and production workloads, identifying application components, filtering resources during troubleshooting, and managing large clusters more consistently, as seen in practical AWS and Kubernetes infrastructure management work. Selectors can use equality matching, such as env=prod, or set-based matching, such as matching Pods where tier is either frontend or backend. Labels should be planned carefully because controllers and Services depend on them; a wrong or missing label can remove a Pod from traffic, leave it unmanaged, or cause automation to target the wrong resource.