Closed Xiol closed 11 months ago
Hi @Xiol
Allocated resources:
(Total limits may be over 100 percent, i.e., overcommitted.)
Resource Requests Limits
-------- -------- ------
cpu 250m (6%) 50m (1%)
memory 150Mi (1%) 190Mi (2%)
ephemeral-storage 0 (0%) 0 (0%)
squat.ai/serial 0 0
squat.ai/temperature 1 1
This snippet indicates that the Kubelet hasn't allocated any serial devices to any pod, which could happen for several reasons: no one is requesting it, none have been discovered, the plugin refused to allocate it, or some combination.
Can you please share more of the node description? I would particularly like to see the part the output that lists the capacity for the node, e.g. total memory, total serial devices, total temperature devices.
Could you also share your pod manifest?
Ahh, it's working now - of course it is.
So when I took the node description for the above, I had the pod getting a squat.ai/temperature
as I was in the process of testing the USB device passthrough after failing with the serial one for some time. Switching this back to squat.ai/serial
now has worked, and the device has been passed through successfully. Having also removed the USB configuration and only left the serial configuration, this also now works.
So, the problem seems to have only existed between the chair and keyboard, although what I was doing wrong is still a mystery to me. Sorry for wasting your time!
I'm glad you got it working ❤️
Hello.
I have a 1-wire USB temperature sensor that sets up /dev/ttyUSB0 as a serial port:
dmesg:
The sensor works fine directly on the host (Raspberry Pi 5 with k3s) using
digitemp
, however the device plugin isn't recognising/dev/ttyUSB0
. If I set up the USB vendor/product codes, they get picked up and passed through successfully, but the container requires/dev/ttyUSB0
rather than using the USB device directly.I've tried only with
/dev/ttyUSB0
, with/dev/ttyUSB*
, with both USB and/dev/ttyUSB0
entries, and none of them will cause the plugin to detect/dev/ttyUSB0
.FWIW the USB device is detected and passed through successfully to the container, but unfortunately I need the serial device instead.
Plugin manifest:
kubectl describe node
:Pod logs for device plugin: