Document 7.5 Operator: Improve description of SSL configuration for templates-based deployments

For a templates-based deployment, there is:

• A service and route for the console
• A service and route for the all protocol port

We didn’t give users access to any of the other acceptors - the ports are exposed but there is no service/route. You couldn’t go directly to AMQP only, Core only, etc.

From discussion with Roddie:

In the case of using a template which uses AMQ_TRANSPORTS/AMQ_PROTOCOLS (I remember we disambiguated these recently and I think AMQ_TRANSPORTS is used in the templates while AMQ_PROTOCOLS is used in the scripts, I'll use AMQ_TRANSPORTS), the templates default to a list which is like 'openwire,amqp,stomp,mqtt,hornetq' meaning all are listed but core. In which case the default 'artemis' all protocol port will exist on 61616, as per broker default, and you'll have a port per protocol listed. The template creates the headless service and gives access to each of these via stable name inside ocp but the template does not create a service per port per pod.