<p>I have created a kubernetes cluster by <code>kubeadm</code> following <a href="https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/" rel="nofollow noreferrer">this official tutorial</a>. Each of the control panel components (apiserver,control manager, kube-scheduler) is a running pod. I learned that kube-scheduler will be using some default scheduling policies (<a href="https://github.com/kubernetes/kubernetes/blob/master/pkg/scheduler/algorithmprovider/defaults/defaults.go" rel="nofollow noreferrer">defined here</a>) when it is created by <code>kubeadm</code>. These default policies are a subset of all available policies (<a href="https://kubernetes.io/docs/concepts/scheduling/kube-scheduler/#scoring" rel="nofollow noreferrer">listed here</a>)</p>

<p>How can I restart the kube-scheduler pod with a new configuration(different policy list)?</p>

<p>The kube-scheduler is a static pod managed by kubelet on the master node. So updating the kube-scheduler manifest file (<code>/etc/kubernetes/manifests/kube-scheduler.yaml</code>) will trigger the kube-scheduler to restart.  </p>
