Please fill in the following information:

Issue description: 

Network Policies affect pod to pod communication within the cluster. They don't affect the ingress controller traffic which is what hitting the route would do. So for ch3 3.6 section it should still
get a response when hitting the route, and not a timeout.

So this:
[student@workstation ~]$ oc rsh $PODNAME curl --max-time 5 \
 hello-web-web-servers.apps.ocp4.example.com | grep Welcome
command terminated with exit code 28

should change to this:
[student@workstation ~]$ oc rsh $PODNAME curl --max-time 5 \
 hello-web-web-servers.apps.ocp4.example.com | grep Welcome

Hello, World! Welcome to Red Hat Training.

The latter is what I am getting after creating the NetworkPolicy and I hit the route. The other
two svc ClusterIP and vmi IP get the timeout as expected. 

Steps to reproduce:

Workaround:

Expected result: