Open lengrongfu opened 1 month ago
If you agree, I will submit the code to the gitlab repository.
However, you can customize the resourceName when deploying the device-plugin component, such as when using MPS.
Can you clarify how you are changing the resource name? Resource renaming is currently not supported in the device-plugin. Additionally, when enabling MPS, the resource name used is still nvidia.com/gpu
.
However, you can customize the resourceName when deploying the device-plugin component, such as when using MPS.
Can you clarify how you are changing the resource name? Resource renaming is currently not supported in the device-plugin. Additionally, when enabling MPS, the resource name used is still
nvidia.com/gpu
.
Oh, I saw this code. Because we forked device-plugin a long time ago for secondary development, we can still modify the resource name.
@cdesiniotis For some historical reasons, our resource names can be modified, but still prefixed with nvidia.com
, so can gpu-operator
be compatible with this situation?
In this method, two resource prefixes
nvidia.com/mig-
andnvidia.com/gpu
are checked on the node. However, you can customize the resourceName when deploying thedevice-plugin
component, such as when using MPS. So this won't work as expected.https://github.com/NVIDIA/gpu-operator/blob/d4316a415bbd684ce8416a88042305fc1a093aa4/validator/main.go#L1240C18-L1240C37
We hope we add a
availablePrefixResourceName
method, it only checknvidia.com
prefix, because device-plugin have a fixed prefix https://github.com/NVIDIA/k8s-device-plugin/blob/5144aa02c97b4aba8c0d118ccee9748834458d21/api/config/v1/consts.go#L25