Section about external client load balancing is misleading:
https://docs.redhat.com/en/documentation/red_hat_amq_broker/7.13/html/deploying_amq_broker_on_openshift/assembly-br-configuring-operator-based-deployments_broker-ocp#con-br-connecting-broker-external-clients_broker-ocp

Current wording is this:

Enable load balancing by configuring the haproxy.router.openshift.io/balance roundrobin option on the OpenShift route for each broker pod.

The wording above suggests to annotate multiple routes and it suggests the routes creation is taken care of by the operator itself.

However the correct procedure to enable this feature is this:

• Create single service MANUALLY matching all the broker pods you want to load-balance across (typically all brokers in a cluster). These distinct broker pods will share these same labels which can be used as selector in the service definition:
  labels:
  ActiveMQArtemis: <CR-NAME>
  application: <CR-NAME>-app
• Expose this Service using OpenShift Route - MANUALLY and add appropriate load balancing annotation : haproxy.router.openshift.io/balance