Tuomas Katila

Thanks for the review @eero-t. I fixed all but two that I objected to.

Rebased against current main. I also verified that everything still works against a real hw.

I'd check the code one more time if I were you. The functions that generate the device spec files should take into account the `prefix`. So if the fake devices/files...

Hi @Serverfrog and thanks for a detailed issue report! Logs seem to indicate plugin working correctly with no errors that would cause things to fail. Installing user space libraries to...

Weird.. everything seems fine from resource point of view. Can you drop GAS so that it doesn't interfere with the scheduling decisions? Make sure to remove the scheduler config part...

> > kube-system intel-gpu-exporter-wwf72 100m (1%) 0 (0%) 100Mi (0%) 500Mi (1%) 6h31m > > Tuomas, what's this? Probably this: https://github.com/onedr0p/intel-gpu-exporter

As the GPU plugin officially only supports one type of GPU per node, the labeling rules do not work with multiple types of GPUs. For example in the count label:...

> > @Serverfrog to summarize, your workload now works with the i915 resource, but the a pod requesting i915_monitor fails? > > exactly. > > Only one would be used,...

Hi @Serverfrog You can increase the GPU plugin logs in the GPU CR by setting `spec.logLevel` to 4. Or add "-v=4" to the GPU plugin deployment's arguments. The operator just...

Yes, the implementation is available, but there are no public container images yet. They will come with our next release in September.