Kubernetes Network Policy
Definition
Kubernetes network policies describe allowed connections of selected application units.
A Kubernetes API resource that describes allowed ingress and egress traffic for selected pods. It becomes effective only if the deployed network plugin supports NetworkPolicy.
Simply explained
A rule defines which application may communicate with which other; the network technology must also enforce it.
Why it matters in practice
Helps develop and operate digital systems robustly, securely, and maintainably.
Example from business
A namespace allows database access only from selected backend pods.
Limits and pitfalls
- Confusing the presence of a policy with actual enforcement or automatic complete isolation; forgetting DNS, egress, and default-deny rules.
Origin & history
NetworkPolicy is part of the Kubernetes networking API and is based on additive ingress and egress rules.
Use in mid-sized companies
- Possible application: A namespace allows database access only from selected backend pods.
Frequently asked questions
What does Kubernetes network policy mean?
A Kubernetes API resource that describes allowed ingress and egress traffic for selected pods. It becomes effective only if the deployed network plugin supports NetworkPolicy.
Which mistakes should be avoided?
Confusing the presence of a policy with actual enforcement or automatic complete isolation; forgetting DNS, egress, and default-deny rules.
Sources
Source checked on 10.10.2026. Editorial application examples are hypothetical; no evidence of real customer results.
Editorially reviewed on: