For any product that offers HTTPS as a transport, I would like to spin that up on OpenShift Online as easy I can for HTTPS with Python and Node.JS. I also want the option to appear in the catalog rather than having to appear in documentation some place that I need to go read and implement in a bunch of steps.

Our MW "ease of use" for the initial experience should be just as simple as all the other HTTPS enabled products in the catalog as welll as matching the simplicity in our competitors like Heroku, AWS BeanStalk, and Google AppEngine.

This is also driven by the knowledge that most developers know they should use HTTPS between the browser and the cloud servers as a best practice.

I understand, given the nature of OpenShift's proxy this may be reduced functionality (loss of http2) but for more robust functionality I can do the extra steps required in the OCP templates. I also understand this means I will not have encryption within our data center.

To make this absolutely clear without talking too much about implementation - this is just the "default" experience in the catalog. If the user asks for extended functionality (HTTP2, routing non-HTTP protocols...) the expectation will be that they will do more involved steps to get that working.