Which Kubernetes objects can be labeled?

Which Kubernetes objects can be labeled?

• A. Nodes only
• B. Pods, Services, Deployments
• C. Namespaces only
• D. PersistentVolumes only

Answer: (B)

Labels are key-value pairs attached to the metadata of Kubernetes objects. They let you identify, group, and select resources efficiently, and they’re used by controllers and Services to manage traffic and updates. Pods, Services, and Deployments all support labeling and rely on it in essential ways. Pods carry labels, which you can set to describe what the pod represents (for example, app=frontend). Services use a labelSelector to route traffic to the pods that match those labels, enabling stable connections to the right pods even as pods are created or replaced. Deployments also attach labels to the pods they manage; these labels tie the Deployment, its ReplicaSets, and the pods together, so scaling and rolling updates apply consistently. In practice, you might label a set of pods with app=frontend and environment=prod, have a Service select those pods via the same labels, and let a Deployment manage their lifecycle. While many other objects can be labeled as well (not just these three), this combination captures the common pattern used in day-to-day Kubernetes management. Other options suggesting labeling is limited to only one object type aren’t accurate because labeling is supported by many Kubernetes objects beyond just those listed.

Labels are key-value pairs attached to the metadata of Kubernetes objects. They let you identify, group, and select resources efficiently, and they’re used by controllers and Services to manage traffic and updates.

Pods, Services, and Deployments all support labeling and rely on it in essential ways. Pods carry labels, which you can set to describe what the pod represents (for example, app=frontend). Services use a labelSelector to route traffic to the pods that match those labels, enabling stable connections to the right pods even as pods are created or replaced. Deployments also attach labels to the pods they manage; these labels tie the Deployment, its ReplicaSets, and the pods together, so scaling and rolling updates apply consistently.

In practice, you might label a set of pods with app=frontend and environment=prod, have a Service select those pods via the same labels, and let a Deployment manage their lifecycle. While many other objects can be labeled as well (not just these three), this combination captures the common pattern used in day-to-day Kubernetes management.

Other options suggesting labeling is limited to only one object type aren’t accurate because labeling is supported by many Kubernetes objects beyond just those listed.