One of the good things about helm in k8s is that modules can be charts can be deployed independently within the same namespace. It would be nice to be able to group IoT edge modules and deploy them independently like a chart within the device. This will allow to have a community driven configured "charts" deployed in IoT Edge, then can communicate with each other thru IoT Edge Hub. If you think this is a good idea, vote so it can be prioritized.1 vote
Right now 'iotedge list' as well as the Portal show a module in 'backoff' state without giving any indication of when the module will be restarted, or how many times in a row the module has failed. It would be very helpful for troubleshooting purposes if that capability could be added.1 vote
It would be nice to have possibility to set upstream IoT Hub (or even Event Hub) to be different as management IoT Hub. Scenario is, that Dev Company is taking care of development and operation of IoT Edge device, but collected data should flow to their customer subscription for further processing. Sure it is possible to connect to different IoT Hub from module and send data that way, but this bypasses routes feature provided by IoT Edge.1 vote
This is an interesting feature we’ve heard from a couple customers; however we’re busy delivering much more fundamental features. I would not expect any traction on this for at least 6 months or a year.
- Don't see your idea?