cluster DNS for Kapua broker

[vap0rtranz]

I could not connect Kura to the Kapua broker via the deploy info script out (so the Openshift route via DNS and port) but could connect via the Openshift clusterIP and pod port for the broker itself instead. Was rather odd because I can connect to the Kapua console via the Openshift route.

Broker URL tcp://172.30.109.163:1883

[ctron]

The broker port must be 31883, as an external node port is being used.

If you have direct access to nodes and pods, then you can also go by 1883, but I wouldn't recommend that.

You can also go with a route configured to the broker. But for this to work you would need to use websockets (ws://host:port or wss://host:port), which can be proxies by OpenShift.

In theory it should be possible to use TLS with SNI as well for plain TCP. But I haven't tried that out yet.

[vap0rtranz]

If you have direct access to nodes and pods, then you can also go by 1883, but I wouldn't recommend that.

Well that is what I did to shove it in for now, and Kapua sees the simulator; but yea I didn't expect you'd say it's recommended ... for several good reasons.

[ctron]

Sometimes the direct approach just works fine 😉