搭建一套k8s集群之后，本地存储化方案选择了阿里巴巴的open-local，没部署open-local，k8s

的kube-scheduler一切正常，只要按照官方文档部署了open-local，k8s的kube-scheduler就会挂掉，不是被kill掉，就是重启异常，默认的10259的端口就会没有了。没法调度pod，经过排查，是open-local默认配置影响了k8s的kube-scheduler，项目的手册中是这样描述的，

If kube-scheduler in your cluster is static pod, Open-Local will run a Job in every master node to edit your /etc/kubernetes/manifests/kube-scheduler.yaml file by default, you can see it in init-job file.

And you can also configure your kube-scheduler manually, especially when kube-scheduler in the cluster are not static pod.

Set .extender.init_job to false in values.yaml before install Open-Local, this will not run init-job.

Create a file, name it kube-scheduler-configuration.yaml, and put it in /etc/kubernetes/ path of every master node.

集群总的kube-scheduler是静态pod，open-local将在每个主节点上运行一个作业来编辑 /etc/kubernetes/manifests/kube-scheduler.yaml,文档地址open-local/kube-scheduler-configuration.md at main · alibaba/open-local · GitHub

配置在open-local-main/helm/values.yaml中

 init_job默认配置是true修改成false.重置k8s就可以了。也可以按照手册上手动配置,这种没测试过。我只是简单的的修改了init_job，测试持久化没问题。