-
Notifications
You must be signed in to change notification settings - Fork 143
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
Issues with the integration of custom plugins into the simulator #311
Comments
/kind bug |
/area simulator |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
I faced same issue and now unable to test my custom plugin. |
/remove-lifecycle stale Sorry for keeping it for a long time. I'll get a time investigating this before our next patch release. |
#332 should fix this issue. outOfTreeRegistries = runtime.Registry{
nodenumber.Name: nodenumber.New,
}
registeredOutOfTreeMultiPointName = []string{
nodenumber.Name,
} |
@sanposhiho Thank you so much for your comment, now |
@tmishina how was this issue fixed? I tried editing the config like the following for the sample NodeNumber plugin-in in /kube-scheduler-simulator/simulator/scheduler/config/plugin.go as suggested above. var (
) I still got the same status code 500 error after I added the NodeNumber plugin in the KubeSchedulerConfiguration via the GUI. Do we have to move /kube-scheduler-simulator/simulator/docs/sample/nodenumber to somewhere? If possible, please give some guidance with more details on how to integrate our custom plugin. When I was trying to integrate my own custom plugin, I got the same error, so I tried the sample NodeNumber plugin but the result was the same even after adding nodenumber.Name inside registeredOutOfTreeMultiPointName = []string{}. What I did for the NodeNumber plugin:
Any other tricks or missing step(s)? @sanposhiho Much appreciated. |
@yz2001zzx Have you specify scheduler config in # The path to a KubeSchedulerConfiguration file.
# If passed, the simulator will start the scheduler
# with that configuration. Or, if you use web UI,
# you can change the configuration from the web UI as well.
kubeSchedulerConfigPath: "docs/sample/debuggable-scheduler/scheduler.yaml"
|
@yz2001zzx Did you solve your problem? I had the same problem as you. I also modified /kube-scheduler-simulator/simulator/scheduler/config/plugin.go and I also modified simulator/config.yaml like @tmishina said but when I add NodeNumber in Web UI I still I get error code 500. |
@a-c-dream Well, can you open another issue with the repro steps? |
Good morning, I have a problem related to adding a custom plugin to the simulator configuration. To integrate the plugin, I followed the instructions provided in the documentation available at this link: ([/~https://github.com/kubernetes-sigs/kube-scheduler-simulator/blob/master/simulator/docs/custom-plugin.md]).
To determine if the issue was with my custom plugin or something else, I tried integrating the sample plugin as instructed, but it still throws an error.
Specifically, when I add the plugin's name to the YAML file and click on apply, a generic 500 error occurs. Checking the command line, it seems that a certain "Wrapped" file is missing, as seen in the screenshots below.
What could be the problem? Is there any additional configuration that needs to be added beyond what is mentioned in the guide?
The text was updated successfully, but these errors were encountered: