You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using k8s-device-plugin in our kubernetes cluster, we found that in MIG mode:
The device plug-in instance corresponding to the newly created GI is not started
The status of the newly created CI in the node is not displayed
When we delete the Pod corresponding to k8s-device-plugin and trigger a rebuild, the resources are displayed normally.
It seems that the newly created MIG resources are not automatically discovered.
The text was updated successfully, but these errors were encountered:
That is correct. The device-plugin needs to be restarted after a MIG reconfiguration.
If you use the GPU operator, this process is automated for you by a component called the mig-manager, so that you don't have to manager this complexity yourself.
Using k8s-device-plugin in our kubernetes cluster, we found that in MIG mode:
When we delete the Pod corresponding to k8s-device-plugin and trigger a rebuild, the resources are displayed normally.
It seems that the newly created MIG resources are not automatically discovered.
The text was updated successfully, but these errors were encountered: