Hiya, thanks for making this very convenient device plugin!
I've used the container in my cluster for almost a year now (Home Assistant / Zigbee radio and prind / 3D printer), and I'm excited to see you've published a chart for it 👍
I don't know exactly what capabilities are given to containers running in a privileged context (like generic-device-plugin), so restraint might be useless. With this caveat, the way the chart proxies lots of host devices, without giving the user the option to choose themselves which paths to proxy, feels a bit overzealous (?). ref:
|
args: |
|
- --device |
|
- | |
|
name: serial |
|
groups: |
|
- paths: |
|
- path: /dev/ttyUSB* |
|
- paths: |
|
- path: /dev/ttyACM* |
|
- paths: |
|
- path: /dev/tty.usb* |
|
- paths: |
|
- path: /dev/cu.* |
|
- paths: |
|
- path: /dev/cuaU* |
|
- paths: |
|
- path: /dev/rfcomm* |
|
- --device |
|
- | |
|
name: video |
|
groups: |
|
- paths: |
|
- path: /dev/video0 |
|
- --device |
|
- | |
|
name: fuse |
|
groups: |
|
- count: 10 |
|
paths: |
|
- path: /dev/fuse |
|
- --device |
|
- | |
|
name: audio |
|
groups: |
|
- count: 10 |
|
paths: |
|
- path: /dev/snd |
|
- --device |
|
- | |
|
name: capture |
|
groups: |
|
- paths: |
|
- path: /dev/snd/controlC0 |
|
- path: /dev/snd/pcmC0D0c |
|
- paths: |
|
- path: /dev/snd/controlC1 |
|
mountPath: /dev/snd/controlC0 |
|
- path: /dev/snd/pcmC1D0c |
|
mountPath: /dev/snd/pcmC0D0c |
|
- paths: |
|
- path: /dev/snd/controlC2 |
|
mountPath: /dev/snd/controlC0 |
|
- path: /dev/snd/pcmC2D0c |
|
mountPath: /dev/snd/pcmC0D0c |
|
- paths: |
|
- path: /dev/snd/controlC3 |
|
mountPath: /dev/snd/controlC0 |
|
- path: /dev/snd/pcmC3D0c |
|
mountPath: /dev/snd/pcmC0D0c |
Could we get a variable in the chart where we can define which paths to proxy, optionally overriding the defaults?
Again, cheers and much appreciated 🙂
Hiya, thanks for making this very convenient device plugin!
I've used the container in my cluster for almost a year now (Home Assistant / Zigbee radio and prind / 3D printer), and I'm excited to see you've published a chart for it 👍
I don't know exactly what capabilities are given to containers running in a privileged context (like generic-device-plugin), so restraint might be useless. With this caveat, the way the chart proxies lots of host devices, without giving the user the option to choose themselves which paths to proxy, feels a bit overzealous (?). ref:
generic-device-plugin/charts/generic-device-plugin/templates/daemonset.yaml
Lines 36 to 94 in 1027bbe
Could we get a variable in the chart where we can define which paths to proxy, optionally overriding the defaults?
Again, cheers and much appreciated 🙂