In Kubernetes, what does an 'Ingress' rule in a NetworkPolicy define?

In Kubernetes, what does an 'Ingress' rule in a NetworkPolicy define?

• A. The traffic allowed to exit from pods
• B. The policy that schedules pods
• C. The ports used by a container image
• D. The traffic allowed to enter to pods

Answer: (D)

Inbound traffic to pods is controlled by an ingress rule in a NetworkPolicy. It specifies which sources are allowed to connect to the selected pods and on which ports and protocols. This is how you implement access control and micro-segmentation: you can permit traffic from specific namespaces, pods, or IP blocks, and restrict it to certain ports. Ingress is about traffic entering the pods, while egress handles outbound traffic. Scheduling is unrelated, and the ports a container exposes come from the container spec, not the policy itself—though a policy can restrict access to those ports. When a pod is selected by a NetworkPolicy, only traffic allowed by its ingress rules is permitted.

Inbound traffic to pods is controlled by an ingress rule in a NetworkPolicy. It specifies which sources are allowed to connect to the selected pods and on which ports and protocols. This is how you implement access control and micro-segmentation: you can permit traffic from specific namespaces, pods, or IP blocks, and restrict it to certain ports. Ingress is about traffic entering the pods, while egress handles outbound traffic. Scheduling is unrelated, and the ports a container exposes come from the container spec, not the policy itself—though a policy can restrict access to those ports. When a pod is selected by a NetworkPolicy, only traffic allowed by its ingress rules is permitted.