Hi Tien,
You just need to create a passthrough route like this:
https://docs.openshift.com/container-platform/3.9/architecture/networking/routes.html#passthrough-termination
For it to work, your swing client needs to use SNI (server name
identification), so that the OpenShift router knows what
Currently, our application is already running on Docker through RMI over
SSL. Therefore, we are able to connect our client to the server via SSL and
RMI using Docker.
What do we have to do in order to make it work with OpenShift, now?
2018-05-02 16:34 GMT+02:00 Joel Pearson
Selectors refer to labels, so it’d be deploymentconfig.metadata.labels.name
SSL/TLS means the client has to support it too. So if there is some option
to run RMI over SSL/TLS then it could work pretty easily. But if it’s not
possible to run server and client that way then yes, nodeports will be
Thank you for the response.
How can I set up SSL/TLS as a connection method on OpenShift that my Client
connects through SSL/TLS to the server? Is that done on the OpenShift
router or where can I do the settings?
Otherwise, I think NodePorts are the easier solution to establish a
connection
If you're using SSL/TLS you could traverse the Router by use Passthrough.
Otherwise, you have to use NodePorts on a Service or something like that.
The Router is generally only really for HTTP, but with passthrough SSL/TLS
just about anything could be running in the pod.
On Wed, May 2, 2018 at
Hi,
we have a application, which is actually running on Wildfly 12.0.0.Final
via Docker.
Now, we would like to put our application on OpenShift with the existing
Dockerfile.
However, our client is using RMI to connect connect to the server. Is it
still possible to run our application on
