Edge Controller • App Engine K8S Cluster K8S Master K8S Node1 K8S Node n KubeBus Virtual Router ... Edge Node KubeBus App Engine EdgeMetadataService Edge Node KubeBus App Engine EdgeMetadataService • Goal • Cloud VM and Edge nodes run as in one cluster • KubeBus Virtual Router • Public Endpoint for Edge connection • Router to connect • Cloud VM subnet • Cloud Container subnet • Edge Node virtual Network, e.g. Flannel 10.244.0.0/16 KubeBus Edge Network: 192.168.6.2 Container ... KubeBus Virtual Router Edge Network IP: 192.168.6.4 EIP: 35.160.180.205 VM IP: 192.168.23.131 192.168.23.130 192.168.23

the client to the local Hub. If found exception, the client will exit and lose messages. rules: Router rules configuration - clientid: [MUST] The Client ID for client to connect with the local Hub among multiple MQTT clients, you need to configure the connect information, topic permission, and router rules. More detailed configuration of Hub service, please refer to Hub service configuration. This 1.1(2018-12-28) New features optimize MQTT Remote module, support multiple remotes and message router add validate subscription config to check MQTT client subscribe result or not Bugfixes isolate

˓→the client to the local Hub. If found exception, the client will exit and lose ˓→messages. rules: Router rules configuration - clientid: [MUST] The Client ID for client to connect with the local Hub subscribe: among multiple MQTT clients, you need to configure the connect information, topic permission, and router rules. More detailed configuration of Hub service, please refer to Hub service configuration. This 1(2018-12-28) 25.1 New features • optimize MQTT Remote module, support multiple remotes and message router • add validate subscription config to check MQTT client subscribe result or not 25.2 Bugfixes

˓→the client to the local Hub. If found exception, the client will exit and lose ˓→messages. rules: Router rules configuration - clientid: [MUST] The Client ID for client to connect with the local Hub subscribe: among multiple MQTT clients, you need to configure the connect information, topic permission, and router rules. More detailed configuration of Hub service, please refer to Hub service configuration. This

the client to the local Hub. If found exception, the client will exit and lose messages. rules: Router rules configuration - clientid: [MUST] The Client ID for client to connect with the local Hub among multiple MQTT clients, you need to configure the connect information, topic permission, and router rules. More detailed configuration of Hub service, please refer to Hub service configuration. This

Network, e.g. Flannel 10.244.0.0/16 KubeBus Edge Network: 192.168.6.2 Container KubeBus Virtual Router Edge Network IP: 192.168.6.4 EIP: 35.160.180.205 VM IP: 192.168.23.131 192.168.23.130 192.168.23

Network, e.g. Flannel 10.244.0.0/16 KubeBus Edge Network: 192.168.6.2 Container KubeBus Virtual Router Edge Network IP: 192.168.6.4 EIP: 35.160.180.205 VM IP: 192.168.23.131 192.168.23.130 192.168.23