Tuomas Katila

> * `memory.max` is split equally, not on actual card capability -> This can cause some issues even when we get the right device type, cards can be overscheduled AFAIK...

> * Add option to GAS for specifying allowed range for GPU resource requests GAS would be a possible place for limiting the i915 resource requests, but that would then...

Hi @cosandr and thanks for the issue! For some plugins we support `annotations` in the CR, this would be similar and definitely doable.

> * Adding NFD rule to taint nodes with given device type I don't understand this. Can you clarify? > * Adding toleration for that taint to corresponding device plugin...

> It's experimental NFD feature: https://nfd.sigs.k8s.io/usage/customization-guide#node-tainting > > NFD worker will then need toleration for that taint too though... We can try them out, document the use and maybe create...

@cosandr & @winromulus question or concern about this request. By the node having a taint and the plugin having a toleration, it would also mean that the workloads would require...

Thanks @winromulus So to summary: run GPU plugin on all nodes with GPU hardware, regardless of the taints. Workloads request the GPU resource + have toleration(s) for the tainted node....

Thanks for reporting this. Did you verify that it's only on docker runtime?

The change that is causing this was introduced on 0.26.1 version. You can workaround it by using 0.26.0 in the mean while.

> Have you tried any newer Docker version? I tried a newer version and it reproduces with it: ``` $ dpkg --list | grep Docker ii docker-buildx-plugin 0.11.2-1~ubuntu.22.04~jammy amd64 Docker...