Support the following requirements:

• One broker with a connection router
• Multiple target brokers for domain specific queues
• Connection router broker selects the correct broker based on CLIENT_ID, based on custom filter logic.  For example, all clients with CLIENT_ID "domain_a" should be routed to broker-2.  NOT based on modulo policy.
• Openshift non-clustered configuration (multiple non-clustered brokers)

This will avoid multiple retries or redirects for a client to end up on the correct broker.  Static pools are not supported today, but a static pool with a custom policy may meet these requirements.

Today, customers have the option of using a local target filter with an OCP load balanced service, which can potentially lead to many reconnect attempts before the client connects to a broker that accepts the connection.  This has the potential to scale poorly with, for example many clients and brokers all doing SSL connections.