You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: kubenetes/network_policy/README.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,3 +10,6 @@ Network policies in Kubernetes are implemented using the Kubernetes Network Poli
10
10
11
11
Ingress rules define the traffic that is allowed to flow into a pod, while egress rules define the traffic that is allowed to flow out of a pod. In addition to specifying the source and destination pods, network policies can also specify other properties such as the protocol (TCP, UDP, etc.), the port number, and the traffic direction (ingress or egress).
12
12
13
+
By using network policies, we can implement a wide range of security and compliance policies to protect the cluster from malicious attacks and unauthorized access. For eg., isolating sensitive workloads, restricting access to specific ports, or blocking traffic from specific IP addresses.
14
+
15
+
To actually enforce the network policy, make sure a 3rd party CNI is installed alongside like Calico, Weave, Flannel, etc.
0 commit comments