text: Finally, if the Pod connects to an external host, the traffic flow from the eth0 interface in the 
  pod to the vethX in the Linux bridge then to the br0 interface in the OVS uses the tun0 
  interface through the eth0 to the physical network. 
  
  Almost all packet delivery decisions are performed with OpenFlow rules in the OVS bridge 
  br0, which simplifies the plug-in network architecture and provides flexible routing. In the case 
  of the ovs-multitenant plug-in, this configuration also provides enforceable network isolation. 
  
  **4.2.3 OpenShift external cluster communication**
  
  OpenShift Container Platform provides different ways to access the applications or services 
  that are running inside the cluster. 
  
  Administrators can make available a service endpoint that external traffic can reach by 
  assigning a unique external IP address to that service from a range of external IP addresses. 
  This IP address range is specified by using a CIDR notation, which allows an application user 
  to make a request against the cluster for an external IP address. 
  
  Each IP address must be assigned to only one service to ensure that each service has a 
  unique endpoint. 
  
  The recommendation, in order or preference, is: 
  
  (cid:2) Use a router if you use HTTP/HTTPS or TLS-encrypted protocol other than HTTPS. 
  (cid:2) Use a Load Balancer, an External IP, or a NodePort. 