Kubernetes network policy is the rule set that governs which pods or namespaces can communicate with one another and under what conditions. It matters because east-west traffic becomes a serious risk when workloads can talk to each other too freely inside the cluster.
What is Kubernetes Network Policy?
Network policy supports segmentation between services, namespaces, and environments. It helps reduce lateral movement, isolate sensitive workloads, and make unintended communication more visible and less accepted by default.
What Kubernetes Network Policy Commonly Supports
Common uses include cluster segmentation, zero-trust networking, multi-tenant isolation, and workload communication control.
Kubernetes Network Policy vs. Flat Cluster Networking
Kubernetes network policy defines explicit communication boundaries. Flat networking allows broader default connectivity across workloads.
Frequently Asked Questions
Why use network policy?
Because clusters become much safer when workloads can reach only the peers they actually need.
Is network policy enough for workload security?
No. Identity, runtime, secrets, and admission controls still matter too.
