How does Kubernetes use labels for resource selection?

How does Kubernetes use labels for resource selection?

• A. Many Kubernetes components use labels to select the resources they should operate on.
• B. Labels define network policies.
• C. Labels determine GPU quotas.
• D. Labels are used to store secret data.

Answer: (A)

Labels are key-value pairs attached to Kubernetes objects that let you describe attributes of those resources and, crucially, pick which ones to act on. This labeling gives many components a flexible way to target the exact set of pods or other resources they should manage. For example, a Service uses a label selector to route traffic only to pods that carry a matching label. A Deployment or ReplicaSet relies on a label selector to manage the pods that belong to its workload. There are also two ways to define the selection: matchLabels for exact key/value matches and matchExpressions for more complex conditions, like in or notin. You can apply or update labels with kubectl or in manifests, so you can dynamically group resources as the cluster evolves. Because labels provide a simple, runtime mechanism to identify resources, Kubernetes uses them broadly for resource selection across components.

Labels are key-value pairs attached to Kubernetes objects that let you describe attributes of those resources and, crucially, pick which ones to act on. This labeling gives many components a flexible way to target the exact set of pods or other resources they should manage. For example, a Service uses a label selector to route traffic only to pods that carry a matching label. A Deployment or ReplicaSet relies on a label selector to manage the pods that belong to its workload. There are also two ways to define the selection: matchLabels for exact key/value matches and matchExpressions for more complex conditions, like in or notin. You can apply or update labels with kubectl or in manifests, so you can dynamically group resources as the cluster evolves. Because labels provide a simple, runtime mechanism to identify resources, Kubernetes uses them broadly for resource selection across components.