Murali Reddy 922c9f5808 GA network policy does not reject if there is not a single source pod matching a policy ...

Fix ensures below two cases are explicitly handled

 - in the network policy spec for the ingress rule, its optionsl to give 'ports' and 'from' details
   when not specified it translates to match all ports, match all sources respectivley

 - user may explicitly give the 'ports' and 'from' details in the ingress rule. But at any given point
   its possible there is no matching pods (with labels defined in 'from') in the namespace.

Before the fix both the cases were handled similarly resulting in unexpected behaviour

Fixes #85

2017-07-29 16:53:52 +05:30

..

network_policy_controller.go

GA network policy does not reject if there is not a single source pod matching a policy

2017-07-29 16:53:52 +05:30

network_routes_controller.go

fix Source/destination check disable logic

2017-07-21 15:20:42 +05:30

network_services_controller.go

fix null pointer dereference during kube-router --cleanup-config

2017-07-27 23:24:03 +05:30