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
Is your feature request related to a problem?/Why is this needed
In early carina releases, disks were registered as a device on Node, but this was removed after Carina v0.10.0, with Nodecrd replacing it
Describe the solution you'd like in detail
Some partners in the community reported that carina-Scheduler could not be used due to multiple schedulers in their cluster. So hopefully there will still be the ability to register disk devices with the nodes so that the scheduling functions of the default scheduler can be used
Describe alternatives you've considered
So we have several options: ① device registration co-exists with Nodecrd; ② open a single scheduling plug-in project based on Webhook
Additional context
The text was updated successfully, but these errors were encountered:
I think we can supply two scheduler extention way: webhook and framework plugin. They can be used as independent modules. Storage should be used as a pluggable peripheral resource, it should be independent of nodes and pods. K8s alreay support csi storage capacity, we should consider this trend and direction.
in my usage scenario,i just want get the disk usage by nodeinfo, not hope to get this infomation from thirdpary crd. so i hope carina can still reserve device plugin mechanism
Is your feature request related to a problem?/Why is this needed
In early carina releases, disks were registered as a device on Node, but this was removed after Carina v0.10.0, with Nodecrd replacing it
Describe the solution you'd like in detail
Some partners in the community reported that carina-Scheduler could not be used due to multiple schedulers in their cluster. So hopefully there will still be the ability to register disk devices with the nodes so that the scheduling functions of the default scheduler can be used
Describe alternatives you've considered
So we have several options: ① device registration co-exists with Nodecrd; ② open a single scheduling plug-in project based on Webhook
Additional context
The text was updated successfully, but these errors were encountered: