Which resource controls network traffic between pods within a namespace?

Which resource controls network traffic between pods within a namespace?

• A. NetworkPolicy
• B. Ingress
• C. Service
• D. Route

Answer: (A)

NetworkPolicy is the mechanism for controlling how pods talk to each other within a namespace. It lets you specify which pods can receive traffic and which pods are allowed to send traffic, using pod selectors and optional namespace scoping, with explicit rules for ingress and egress. This control is enforced by the cluster’s networking plugin, so only traffic that matches the policy is allowed. Other resources don’t govern inter-pod traffic. Ingress handles external HTTP routing into the cluster, Route exposes services to the outside world in OpenShift, and a Service provides a stable endpoint for a group of pods but does not impose policy on traffic between pods.

NetworkPolicy is the mechanism for controlling how pods talk to each other within a namespace. It lets you specify which pods can receive traffic and which pods are allowed to send traffic, using pod selectors and optional namespace scoping, with explicit rules for ingress and egress. This control is enforced by the cluster’s networking plugin, so only traffic that matches the policy is allowed.

Other resources don’t govern inter-pod traffic. Ingress handles external HTTP routing into the cluster, Route exposes services to the outside world in OpenShift, and a Service provides a stable endpoint for a group of pods but does not impose policy on traffic between pods.