-
Notifications
You must be signed in to change notification settings - Fork 145
[问题] Device Plugin allocate 选出的 pod 是否会跟 Kubelet 绑定的不一致 #16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
这里依赖是Pod在调度器是按顺序bind的,而且在bind过程中已经加了锁。是能够保证顺序性的。 |
@cheyang |
是的,这里实现可能会造成不一致。kubelet device plugin allocate 是按照 container 调用,但在 gpushare-device-plugin 是按照自有逻辑找到 candidate pod,不一定是 kubelet 调用的那个 pod。并且如果单 pod 下有多个 container 申请了 gpu 资源,这里肯定匹配不到。 gpushare-device-plugin/pkg/gpu/nvidia/allocate.go Lines 54 to 88 in 5b68fe2
|
|
看 Kubelet 调用 allocate 的实现
deviceplug.allocate
会但是在
Kubelet
调用deviceplug.allocate
时已经确定了podUID
. 两者是否会不同?The text was updated successfully, but these errors were encountered: