Fuse 7 OpenShift console should support a per-network zone deployment model

At present, the Fuse 7 console can be deployed on OpenShift in a cluster-wide or per-namespace model. Neither model supports a set-up where the compute nodes are deployed in distinct network zones. An installation might have, for example, "production" and "development" zones that are completely isolated from one another; of course, both zones are accessible, to some extent, from the control plane nodes.

Even when the console is installed in a cluster-wide configuration, it still has to be serviced by some compute node – we can't run it in the control plane. But with a multi-zone set-up this doesn't work, because the Jolokia ports on the Fuse pods the console needs are inaccessible.

Similar set-ups might exist in multi-tenant OpenShift configurations.

 What's needed is some way to install a console in each network zone, such that it can monitor all namspaces in that zone.