-
Notifications
You must be signed in to change notification settings - Fork 67
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
mapper映射器 #106
Comments
I think you can abstract a machine node into a device, use CRD to describe the attributes of your node. Your idea is very interesting, welcome to continue providing some details. :) |
I have considered this approach, but I am uncertain if the nodes support CRDs. Additionally, there are differences in the way devices and nodes operate |
CRD has some custom fields that allow developers to customize thier device, u can find some example in this, for example random-device-instance.yaml and random-device-model.yaml implemented a virtual device that generates random numbers. For another question, I think that u can establish a server on the node, which collects indicators that need to be reported to kubeedge. The mapper can obtain and change the corresponding data through the |
Alright, thank you very much. |
Can Kubeedge currently map a machine node through the current mapper
The text was updated successfully, but these errors were encountered: