CSINodes problem in Kubernetes Multiple Scheduler

finally I try to use the old version of kubernetes before 16.3, I am using 15.6 and it works now – akhmad alimudin

OK, now I understand what was the cause of the issue you experienced. You probably tried to run newer kube-scheduler version on the a bit older k8s cluster (where the key component is kube-apiserver) which cannot be done. As you can read in the official kubernetes documentation:

kube-controller-manager, kube-scheduler, and cloud-controller-managermust not be newer than the kube-apiserver instances they communicate with. They are expected to match the kube-apiserver minor version, but may be up to one minor version older (to allow live upgrades).

Example:

kube-apiserver is at 1.13 kube-controller-manager, kube-scheduler, and cloud-controller-manager are supported at 1.13 and 1.12

So you can use kube-scheduler which is one minor version older than your currently deployed kube-apiserver but not newer.

@mario is right, I hit the same issue, my original kubernates version is v1.16.3 and I use Scheduler-Framework of k8s which is v1.17.x.

I test my new scheduler on another k8s cluster with v1.17.x, it could work.