-
Notifications
You must be signed in to change notification settings - Fork 38.6k
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
DRA: no handler registered for plugin type: DRAPlugin at socket /var/lib/kubelet/plugins_registry/ #124962
Comments
/sig node |
/assign |
Here is such a plugin: https://github.com/kubernetes/kubernetes/blob/master/test/e2e/dra/test-driver/app/kubeletplugin.go#L143 and it's used heavily in the DRA e2e and e2e_node tests and registers just fine. Can you provide more details so I can investigate the issue further? |
Hi @bart0sh, thanks for the response!
Yes, the k8s version info is shown below:
and the codebase of my plugin is here: https://github.com/spidernet-io/spiderpool/blob/0d8872cdb891dde80ef1cc86fb195ee31e126ce4/pkg/dra/dra-plugin/plugin.go#L37 and the version of the dra library I used is v0.29.2: https://github.com/spidernet-io/spiderpool/blob/0d8872cdb891dde80ef1cc86fb195ee31e126ce4/go.mod#L61 and the sock file of my plugin is here:
and the error logs of the plugin is show below:
Please let me know if there is any other information you would like me to provide :) |
@cyclinder I'm not able to reproduce this with the below code and with the hacked version of spiderpool code.
Here is what I see in the kubelet log:
Can you try to run either of those in your environment just to see if it's still reproducible? |
Thanks @bart0sh for looking at this! I tried to run your branch in my environment, but it still failed with the same error:
show the kubelet logs:
Can you tell me which k8s version you use in your environment? |
@cyclinder Can you reproduce this with a dev cluster if you run it this way from the v1.29.1 k/k source tree. ?
|
@cyclinder I tried to use exactly the same versions as you've mentioned above. Here is my go.mod for the code I've shown above:
k/k version is 1.29.1 |
@cyclinder
It looks like Kubelet can't connect to the plugin socket for some reason. It would make sense to run Kubelet with a higher verbosity level to get more info. |
Nope, It doesn't relate to this issue, I believe this line of the log has misled you. I used
Yes, I will be trying to reproduce this later and give feedback to you. |
/triage accepted |
@cyclinder I have another guess. You probably didn't enable DynamicResourceAllocation feature gate. This explains why the handler is not registered. Can you show your kubelet command line? |
woo, thanks for the tips, I enabled the DynamicResourceAllocation feature gate via kubelet flag before, but It didn't work, and after I added the feature-gates into
Thanks @bart0sh for the help! Let me close the issue. /close |
@cyclinder: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
What happened?
What did you expect to happen?
handling request well
How can we reproduce it (as minimally and precisely as possible)?
write a dra kubelet-plugin with
kubeletplugin.Start()
Anything else we need to know?
No response
Kubernetes version
Cloud provider
OS version
Install tools
Container runtime (CRI) and version (if applicable)
Related plugins (CNI, CSI, ...) and versions (if applicable)
The text was updated successfully, but these errors were encountered: