Kai Zimmermann

@stefbehl thx for opening the thread. You might be interested in this read https://github.com/kaizimmerm/hawkbit-extensions/blob/feature-azure-iot-hub/hawkbit-extensions-azure/hawkbit-extension-azure-iot-hub/WhitepaperAzureIoThawkBit.md It is about Azure IoT but I assume applicable to other IoT connectivity layers and device...

I think what needs to be done after #242 is that devices by DDI or DMF as well can report offline updates by identifying DS by name, version.

I agree with @schabdo . Keep in mind that auto assignment was primarily intended to be used for initial device provisioning. Rollout management is the right tool for later deployments.

Hi, its `ORG_ECLIPSE_HAWKBIT_REPOSITORY_AZURE_CONNECTION_STRING` you can see all the variables here: https://github.com/eclipse/hawkbit-extensions/blob/master/hawkbit-extended-runtimes/hawkbit-update-server-azure/deployment/helm/hawkbit/templates/deployment.yaml

@schabdo there is no k8s dependency in the docker image.