<p>I try to create multiple scheduler running on kubernetes following this instruction <a href="https://kubernetes.io/docs/tasks/administer-cluster/configure-multiple-schedulers/" rel="nofollow noreferrer">https://kubernetes.io/docs/tasks/administer-cluster/configure-multiple-schedulers/</a>
the new kubernetes scheduler status is <strong>running</strong> but the logs generate this error, and the pods that using the new scheduler status is <strong>pending</strong> </p>

<pre><code>E1129 02:43:22.639372       1 reflector.go:156] k8s.io/client-go/informers/factory.go:135: Failed to list *v1.CSINode: the server could not find the requested resource
</code></pre>

<p>and this is my clusterrole of kube-scheduler</p>

<pre><code>apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  annotations:
    rbac.authorization.kubernetes.io/autoupdate: "true"
  creationTimestamp: "2019-11-28T08:29:43Z"
  labels:
    kubernetes.io/bootstrapping: rbac-defaults
  name: system:kube-scheduler
  resourceVersion: "74398"
  selfLink: /apis/rbac.authorization.k8s.io/v1/clusterroles/system%3Akube-scheduler
  uid: 517e8769-911c-4833-a37c-254edf49cbaa
rules:
- apiGroups:
  - ""
  - events.k8s.io
  resources:
  - events
  verbs:
  - create
  - patch
  - update
- apiGroups:
  - ""
  resources:
  - endpoints
  verbs:
  - create
- apiGroups:
  - ""
  resourceNames:
  - kube-scheduler
  - my-scheduler
  resources:
  - endpoints
  verbs:
  - delete
  - get
  - patch
  - update
- apiGroups:
  - ""
  resources:
  - nodes
  verbs:
  - get
  - list
  - watch
- apiGroups:
  - ""
  resources:
  - pods
  verbs:
  - delete
  - get
  - list
  - watch
- apiGroups:
  - ""
  resources:
  - bindings
  - pods/binding
  verbs:
  - create
- apiGroups:
  - ""
  resources:
  - pods/status
  verbs:
  - patch
  - update
- apiGroups:
  - ""
  resources:
  - replicationcontrollers
  - services
  verbs:
  - get
  - list
  - watch
- apiGroups:
  - apps
  - extensions
  resources:
  - replicasets
  verbs:
  - get
  - list
  - watch
- apiGroups:
  - apps
  resources:
  - statefulsets
  verbs:
  - get
  - list
  - watch
- apiGroups:
  - policy
  resources:
  - poddisruptionbudgets
  verbs:
  - get
  - list
  - watch
- apiGroups:
  - ""
  resources:
  - persistentvolumeclaims
  - persistentvolumes
  verbs:
  - get
  - list
  - watch
- apiGroups:
  - authentication.k8s.io
  resources:
  - tokenreviews
  verbs:
  - create
- apiGroups:
  - authorization.k8s.io
  resources:
  - subjectaccessreviews
  verbs:
  - create
- apiGroups:
  - storage.k8s.io
  resources:
  - csinodes
  verbs:
  - watch
  - list
  - get
</code></pre>

<p>is there any suggestion of this problem?</p>

<p>Thank you</p>

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

<p>OK, now I understand what was the cause of the issue you experienced. You probably tried to run newer <code>kube-scheduler</code> version on the a bit older k8s cluster (where the key component is <code>kube-apiserver</code>) which cannot be done. As you can read in the <a href="https://kubernetes.io/docs/setup/release/version-skew-policy/#kube-controller-manager-kube-scheduler-and-cloud-controller-manager" rel="nofollow noreferrer">official kubernetes documentation</a>:</p>

<blockquote>
  <p><code>kube-controller-manager</code>, <code>kube-scheduler</code>, and <code>cloud-controller-manager</code>
  <strong>must not be newer</strong> than the <code>kube-apiserver</code> instances they communicate
  with. They are expected to match the <code>kube-apiserver</code> <strong>minor version</strong>, but
  may be up to one minor version older (to allow live upgrades).</p>
  
  <p>Example:</p>
  
  <p><code>kube-apiserver</code> is at <strong>1.13</strong> <code>kube-controller-manager</code>, <code>kube-scheduler</code>, and
  <code>cloud-controller-manager</code> are supported at <strong>1.13</strong> and <strong>1.12</strong></p>
</blockquote>

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