Replies: 1 comment
-
That's not what it should do. As soon as you add a policy that matches a pod, only traffic matching the policy is allowed. The rule you've created will only allow traffic from 10.2.201.0/24, except 10.2.201.113. All other traffic will be blocked because it does not match any other ingress rules. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm trying to configure a Networkpolicy that should block Network-traffic from a specific external IP-address.
So the Network-range I specified here, is not the IP-range that is used internally in the K3s cluster, but in the network where also K3s is running. For some reason this is blocking all traffic from any IP-address outside of the cluster to all pods with the label service. But it should block it only for the one IP address is specified in the except list.
Is this feature supported by the Kuberouter at all, or is it only for handling traffic between the pod, when they are talking directly with each other over internal network?
Beta Was this translation helpful? Give feedback.
All reactions