K8s Controllers & Communication Connectors

Discussions and issues as well as technical advice for handling the registration of devices as DeviceNodes and the registration of user-submitted applications as Applications in the etcd K8s database. Custom Resource Definitions are used one per abstraction entity (DeviceNode & Application).

Advertised devices are registered as DeviceNodes by creating the corresponding K8s Custom Resource. Same for the Application.

Communication Connectors intercept messages from devices for the following:

• registering the device as DeviceNode.
• monitoring DeviceNode status.
• schedule/delegate a submitted application to a DeviceNode.
• monitoring the status of the applications.

AsyncAPI specifications is created for the purposes of the above and MQTT is selected to be used as communication protocol.