Broker created by OpenShift operator does not support "oc port-forward"

OpenShift provides a port-forwarding mechanism to tunnel traffic into pods for diagnostic purposes. This facility provides a way to attach test clients, etc., without being blocked by firewalls and the rest of the OpenShift virtual network infrastructure.

Port-forwarding does not work, when trying to connect to broker ports, when the broker was created by the OpenShift operator. That's because the operator creates acceptors that bind only to a specific hostname, and the port-forwarding machinery always connects to "localhost" from within the pod.

A conventional stand-alone installation of AMQ 7 will create acceptors that bind to "0.0.0.0", that is, capable of accepting connections on any interface. The same configuration should be present in AMQ 7 pods or, at least, enabled easily via the operator.