What is the primary function of NetworkPolicies in Kubernetes?

What is the primary function of NetworkPolicies in Kubernetes?

• A. To classify Pods as isolated and control their communication
• B. To route external traffic to services
• C. To aggregate metrics from pods
• D. To configure storage classes

Answer: (C)

NetworkPolicies define how pods can communicate with each other and with other network endpoints. They select pods using labels and then specify allowed ingress and/or egress rules, including which peers, ports, and protocols are permitted. When a Pod is selected by a NetworkPolicy, it becomes isolated from traffic that isn’t explicitly allowed, enforcing network segmentation and security boundaries within the cluster. This is about pod-to-pod communication control, not about routing external traffic (that’s handled by Ingress/Services), metrics collection, or storage configuration.

NetworkPolicies define how pods can communicate with each other and with other network endpoints. They select pods using labels and then specify allowed ingress and/or egress rules, including which peers, ports, and protocols are permitted. When a Pod is selected by a NetworkPolicy, it becomes isolated from traffic that isn’t explicitly allowed, enforcing network segmentation and security boundaries within the cluster. This is about pod-to-pod communication control, not about routing external traffic (that’s handled by Ingress/Services), metrics collection, or storage configuration.