Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Openshift V3: Confusion on Services and Routes

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

The description in service says that:

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.

it can forward TCP/UDP stream while description in routes says:

Routers support the following protocols:

HTTP

HTTPS (with SNI)

WebSockets

TLS with SNI

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

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.

EDIT Tagged Kubernetes because it is also used within and may be someone from them can help.

Thanks

like image 329
user3275095 Avatar asked Nov 21 '15 01:11

user3275095


People also ask

What is difference between route and service in OpenShift?

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.

What is the purpose of a route in OpenShift?

A route allows you to host your application at a public URL. It can either be secure or unsecured, depending on the network security configuration of your application.

What is passthrough route?

With passthrough termination, encrypted traffic is sent straight to the destination without the router providing TLS termination. Therefore no key or certificate is required on the route. Prerequisites. You must have a service that you want to expose.


1 Answers

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.

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.

like image 163
Clayton Avatar answered Oct 11 '22 04:10

Clayton