After applying a NetworkPolicy to restrict traffic to Pods labeled role=frontend, backend Pods still receive traffic from other Pods. What is the most probable cause?
medium📝 Troubleshoot Q6 of 15
Kubernetes - Networking
After applying a NetworkPolicy to restrict traffic to Pods labeled role=frontend, backend Pods still receive traffic from other Pods. What is the most probable cause?
AThe NetworkPolicy does not select the backend Pods correctly
BThe cluster network plugin does not support NetworkPolicies
CNetworkPolicy rules are applied only to Services, not Pods
DNetworkPolicies allow all traffic by default and cannot restrict it
Step-by-Step Solution
Solution:
Step 1: Verify NetworkPolicy enforcement
NetworkPolicies require cluster network plugin support to enforce rules.
Step 2: Check cluster network plugin
If the plugin lacks support, policies won't restrict traffic despite correct YAML.
Final Answer:
The cluster network plugin does not support NetworkPolicies -> Option B
Quick Check:
NetworkPolicy enforcement depends on network plugin support [OK]
Quick Trick:NetworkPolicies need supported network plugins [OK]
Common Mistakes:
Assuming NetworkPolicies apply to Services only
Believing NetworkPolicies restrict traffic by default
Ignoring network plugin capabilities
Master "Networking" in Kubernetes
9 interactive learning modes - each teaches the same concept differently
