<p>I am going through the Openshift V3 documentation and got confused by services and routes details.</p>

<p>The description in <a href="https://docs.openshift.org/latest/architecture/infrastructure_components/kubernetes_infrastructure.html#service-proxy" rel="noreferrer">service</a> says that:</p>

<blockquote>
  <p>Each node also runs a simple network proxy that reflects the services defined in the API on that node. This allows the node to do simple TCP and UDP stream forwarding across a set of back ends.</p>
</blockquote>

<p>it can forward TCP/UDP stream while description in <a href="https://docs.openshift.org/latest/architecture/core_concepts/routes.html#routers" rel="noreferrer">routes</a> says:</p>

<blockquote>
  <p>Routers support the following protocols:</p>
  
  <p>HTTP</p>
  
  <p>HTTPS (with SNI)</p>
  
  <p>WebSockets</p>
  
  <p>TLS with SNI</p>
</blockquote>

<p>Basically, my requirement is to run an SIP application which runs over UDP and port 5060. </p>

<p>Please help me understand what is meant by service and route in the above context and can I deploy my application on Openshift V3. I found few related questions but those are fairly old.</p>

<p><strong>EDIT</strong>
Tagged Kubernetes because it is also used within and may be someone from them can help.</p>

<p>Thanks</p>

<p>Routes are http, HTTPS, or TCP wrapped with TLS.  You can use a service with a "node port", which load balances your app instances over TCP or udp at a high port exposed on each node.  </p>

<p>Routes point to services to get their source data, but since routes expect to be able to identify which backend service to route traffic to by looking at the incoming HTTP Host header or TLS SNI info, routes today only support those protocols.  </p>
