xpumanager sidecar version issues about intel-device-plugins-for-kubernetes HOT 5 CLOSED

Currently the only use for the xpumanager sidecar is to allow GAS to to schedule Pods to GPUs that are interconnected with xelinks. Flex series doesn't benefit from that.

For the versions. Xpu-manager fixed a bug related to the xelink topology metrics with the 1.2.16 version. But that image hasn't been released yet. Though, the bug is related to dynamic changes of the xelinks and somewhat hard to reproduce. So 1.2.13 is ok for the intermediate.

For the createcontainererror, I think I've seen that and it was related to a change in the file structure in the xpu-manager container. I'll get back to this.

For intel/xpumanager#64, I haven't seen this.

from intel-device-plugins-for-kubernetes.

Got it, thanks for clarifying. We used xpumanager with v1.2.0_golden with sidecar and GPU plugin 0.26.1 and Flex 140 to get GPU utilization metrics. To avoid, createcontainererror, used 1.2.13 with the dockerhub image with same image tag. But see the issue 64. So for Flex, can I assume just deploying the xpumanager daemonset directly should suffice. Is this correct?

from intel-device-plugins-for-kubernetes.

So for Flex, can I assume just deploying the xpumanager daemonset directly should suffice. Is this correct?

Yes, xpumanager-sidecar doesn't add anything for the Flex series.

from intel-device-plugins-for-kubernetes.

@vbedida79 ok to close this?

from intel-device-plugins-for-kubernetes.

yes. thank you

from intel-device-plugins-for-kubernetes.