[Hawkular-dev] Lots of activemq warnings in Kubernetes

Just an FYI. We are running 3 separate instances (aka pods) of Hawkular in our Kubernetes cluster. I started seeing a lot of warnings in the log where DiscoveryNetworkConnector from one container attempts to connect to the other two. I'm not sure if these warnings have any undesirable effects. Viet --- 00:22:18,851 WARN [org.apache.activemq.network.DiscoveryNetworkConnector] (Notifier-MulticastDiscoveryAgent-listener:DiscoveryNetworkConnector:NC:BrokerService[org.hawkular.bus.broker.hawkular-one]) Could not start network bridge between: vm://org.hawkular.bus.broker.hawkular-one?async=false&network=true and: tcp://hawkular-one-qe:62626 due to: hawkular-one-qe 00:22:19,343 INFO [org.apache.activemq.network.DiscoveryNetworkConnector] (Notifier-MulticastDiscoveryAgent-listener:DiscoveryNetworkConnector:NC:BrokerService[org.hawkular.bus.broker.hawkular-one]) Establishing network connection from vm://org.hawkular.bus.broker.hawkular-one?async=false&network=true to tcp://hawkular-one-dev:62626 00:22:19,345 INFO [org.apache.activemq.network.DemandForwardingBridgeSupport] (ActiveMQ BrokerService[org.hawkular.bus.broker.hawkular-one] Task-497) org.hawkular.bus.broker.hawkular-one Shutting down 00:22:19,348 INFO [org.apache.activemq.network.DemandForwardingBridgeSupport] (ActiveMQ BrokerService[org.hawkular.bus.broker.hawkular-one] Task-497) org.hawkular.bus.broker.hawkular-one bridge to Unknown stopped