Re: Route on Service : RPC CALL

2016-09-20 Thread Clayton Coleman 
Are your RPC calls based on HTTP, or a binary protocol?  The router only
supports traffic over HTTP, HTTPS, or TLS with Server-Name-Indication.

If you need to access a service from outside the cluster for non-HTTP
traffic generally you would create a service of type NodePort (which gives
you a port on all hosts) and to have your router machines act as your
gateways.  I.e. your service would be type NodePort, you'd get port 31000,
and then you could access "mycompany.com:31000" (the wildcard you assigned
to the routers) which would connect to your pods on the backend port.

On Tue, Sep 20, 2016 at 10:16 AM, Den Cowboy  wrote:

> Hi,
>
>
> We have a container which is exposing a port . We have to perform RPC
> calls on it.
> I can create a route on the port (https -> 8080) (map it on ) but this
> does not seem to work.
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Route on Service : RPC CALL

2016-09-20 Thread Den Cowboy 
Hi,


We have a container which is exposing a port . We have to perform RPC calls 
on it.
I can create a route on the port (https -> 8080) (map it on ) but this does 
not seem to work.
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users