What is the purpose of labeling in Kubernetes?

What is the purpose of labeling in Kubernetes?

• A. To enforce network policies
• B. To set CPU limits
• C. To designate attributes for grouping and selection
• D. To set memory quotas

Answer: (C)

Labels in Kubernetes are a way to attach attributes to objects as key-value pairs, enabling grouping and selection across the cluster. You can tag resources (like pods, services, or deployments) with labels such as app=frontend or env=prod. This lets you treat all resources with a given label as a group, and lets controllers and tools pick that group with label selectors. For example, a Service can route traffic to pods whose labels match its selector, and you can quickly filter resources with commands like kubectl get pods -l app=frontend. These labels are not about setting resource limits or enforcing network rules; CPU/memory settings pertain to container resources, and network policies are separate objects that control traffic. By design, labels provide flexible organization and precise selection to manage even large clusters.

Labels in Kubernetes are a way to attach attributes to objects as key-value pairs, enabling grouping and selection across the cluster. You can tag resources (like pods, services, or deployments) with labels such as app=frontend or env=prod. This lets you treat all resources with a given label as a group, and lets controllers and tools pick that group with label selectors. For example, a Service can route traffic to pods whose labels match its selector, and you can quickly filter resources with commands like kubectl get pods -l app=frontend. These labels are not about setting resource limits or enforcing network rules; CPU/memory settings pertain to container resources, and network policies are separate objects that control traffic. By design, labels provide flexible organization and precise selection to manage even large clusters.