anchor.diff:  
   Repeating the test in shell 2 again should now be successful:
   
  -  / # wget -S http://http-echo.ns-1.svc.cluster.local/test4 --post-data '{"message":"hello"}'
  -  Connecting to http-echo.ns-1.svc.cluster.local (100.64.161.56:80)
  -    HTTP/1.1 200 OK
  -    X-Powered-By: Express
  -    Content-Type: application/json; charset=utf-8
  -    Content-Length: 536
  -    ETag: W/"218-xgvU8WZSN+2SEyOX6Q2R/AhLuRM"
  -    Date: Thu, 26 Oct 2017 02:15:32 GMT
  -    Connection: close
  -    
  -  test4                100% |*************************************************************************************************|   536   0:00:00 ETA
  +```
  +/ # wget -S http://http-echo.ns-1.svc.cluster.local/test4 --post-data '{"message":"hello"}'
  +Connecting to http-echo.ns-1.svc.cluster.local (100.64.161.56:80)
  +  HTTP/1.1 200 OK
  +  X-Powered-By: Express
  +  Content-Type: application/json; charset=utf-8
  +  Content-Length: 536
  +  ETag: W/"218-xgvU8WZSN+2SEyOX6Q2R/AhLuRM"
  +  Date: Thu, 26 Oct 2017 02:15:32 GMT
  +  Connection: close
  +  
  +test4                100% |*************************************************************************************************|   536   0:00:00 ETA
  +```
   
   == Teardown
   
  
positive.code: 
  When running the following command again in shell 2, we should see it eventually timeout and fail:
  
    / # wget -S http://http-echo.ns-1.svc.cluster.local/test2 --post-data '{"message":"hello"}'
    Connecting to http-echo.ns-1.svc.cluster.local (100.64.161.56:80)
      HTTP/1.1 200 OK
      X-Powered-By: Express
      Content-Type: application/json; charset=utf-8
      Content-Length: 536
      ETag: W/"218-ejthHoYRVZ+oS3p9I5V2qGn/CbM"
      Date: Thu, 26 Oct 2017 02:12:57 GMT
      Connection: close
      
    test2                100% |*************************************************************************************************|   536   0:00:00 ETA
  
  TODO: Issue #
  
  === Create network policy with a rule
  
  
negative.code:   / # 
  +
  . We will now attempt to call the `http-echo` pod from our `busybox` pod by performing an HTTP POST .  As we have no network policies in place, we should see the following command return successfully with a 200 response, along with a log message being output in the `http-echo` shell window:
  +
  ```
  / # wget -S http://http-echo.ns-1.svc.cluster.local/test --post-data '{"message":"hello"}'
  Connecting to http-echo.ns-1.svc.cluster.local (100.71.77.153:80)
    HTTP/1.1 200 OK
    X-Powered-By: Express
    Content-Type: application/json; charset=utf-8
    Content-Length: 533
    ETag: W/"215-KyoPN1JoGjQlzW9TxpIay22VPF8"
    Date: Thu, 26 Oct 2017 00:53:21 GMT
    Connection: close
    
  test                 100% |*************************************************************************************************|   533   0:00:00 ETA
  ```
  HTTP POST request succeeds.
  
  === Create default network policy
  