Closed Yicheng-Lu-llll closed 5 months ago
Hi, @Yicheng-Lu-llll , thanks for sending your issues.
customnoderesource
is defined in https://github.com/kubewharf/katalyst-api
, it will be used by several repos in kubewharf org, so we don't re-define it in godel-scheduler-api
repo.https://github.com/kubewharf/godel-scheduler/blob/main/manifests/base/crds/node.katalyst.kubewharf.io_customnoderesources.yaml
, you can apply it directly in order to make the components work@yuey002 can you help update our quickstart doc when you have time ?
I see, Thank you!
@Yicheng-Lu-llll fyi: installation guide is added to README file in this MR: https://github.com/kubewharf/godel-scheduler/pull/17
When I attempted to follow the instructions in dev-quickstart.md, I noticed that in the "Generate the required CRDs" step, only three CRDs were generated as shown below:
However, the instructions imply there is another CRD: "customnoderesource." The absence of this CRD will prevent the dispatcher, scheduler and binder from starting, as evidenced by the error message below:
After inspecting, it appears that there do have only three CRDs defined here: https://github.com/kubewharf/godel-scheduler-api/tree/main/pkg/apis. Perhaps
customnoderesource
should also be uploaded to the godel-scheduler-api repository? I believe it is used to store topology infomation.