Having an external route for mongo about mongodb-container HOT 10 CLOSED

Ok. So this issue is waiting for SSL support in mongodb-container. And that is blocked by s2i support - #239

from mongodb-container.

any updates on this?

from mongodb-container.

i don't know enough about mongo to advise you about enabling sni (but if you do, you should be able to create a passthrough route to it), but another option would be configuring either an external ip service, or a nodeport for your mongodb pod.

from mongodb-container.

Using SNI does not require using SSL/TLS on the server too?

Currently it is not possible to enable SSL for mongodb container - I plan to add this after s2i support is added (#239)

from mongodb-container.

Using SNI does not require using SSL/TLS on the server too?

yes, it does. I figured that was implied when I said enabling SNI.

from mongodb-container.

yes, it does. I figured that was implied when I said enabling SNI.

Not sure we talk about same "server" :-) I thought a mongod server... I was asking because I am not familiar with "Edge Termination" of OpenShift routes. And if this can be somehow used.

from mongodb-container.

edge termination of a route means the router terminates the SSL connection and then uses a non-encrypted connection to the backend.
https://docs.openshift.org/latest/architecture/core_concepts/routes.html#secured-routes

from mongodb-container.

@bparees So it is possible to connect to service port (different than 80/443) without encrypted connection?

from mongodb-container.

@bparees So it is possible to connect to service port (different than 80/443) without encrypted connection?

services can be on any port you want and any protocol you want. but routes cannot.

from mongodb-container.

mongodb container is not maintained any more in this org. closing.

from mongodb-container.