Helm: Enable multiple separate udev configurations

[melinda-mytra]

Is your feature request related to a way you would like Akri extended? Please describe.
I want to apply different broker jobs to different USB device types. Currently I can only specify one udev configuration. If I've totally misunderstood this, please point me the right way.

Describe the solution you'd like
Make configurations under udev an iterable, so you can generate multiple seperate named udev configurations from values.yaml. E.g.

  udev:
    discovery:
      enabled: true
    configurations:
    -   name: akri-udev-stm
        capacity: 2
        enabled: true
        brokerJob:
          image:
             repository: "broker-x"
        discoveryDetails:
          udevRules:
            - 'SUBSYSTEM=="usb", ATTR{idVendor}=="xxx", ATTR{idProduct}=="xxx"'
    -   name: akri-udev-camera
        capacity: 4
        enabled: true
        brokerJob:
          image:
             repository: "broker-y"
        discoveryDetails:
          groupRecursive: true
          udevRules:
            - 'SUBSYSTEM=="usb", ATTR{idVendor}=="yyy", ATTR{idProduct}=="yyy"'

Describe alternatives you've considered

• Using multiple udev rules: This doesn't enable running different brokers by device type
• Creating my own templates for additional udev configurations and brokers: will try

Additional context
Add any other context or screenshots about the feature request here.

[kate-goldenring]

@melinda-mytra rather than trying to do more with the Helm templates, i'd recommend using helm template to generate each udev configuration and then applying the Yaml files. Does this documentation help https://docs.akri.sh/user-guide/customizing-an-akri-installation#generating-modifying-and-applying-a-configuration?

[melinda-mytra]

Thanks for the docs, that makes sense.
I do think it would be handy to have built in natively, although it's by no means a showstopper - a "nice to have". I haven't checked how complex it would be to do, so if the tradeoff isn't worth it happy to close this.

[kate-goldenring]

I think i am always in favor of simplifying helm templates and charts and have found that in production, most people do not use charts to create custom resources, so I'll close this for now.