An Open Source Graph Database made for the cloud.

NebulaGraph

we are using the default scheduler of k8s(this is reflected with CRD `schedulerName: default-scheduler`), before k8s 1.16, we need to use `nebula-scheduler`  instead.

The only reason that we created nebula-scheduler(by default not used) was to add the even spread support, which, is now the default spread policy in the default scheduler, and when the constraint cannot be fulfilled, it wont schedule pod.

If, we would like to change schedule policy(when node number is not enough for test purposes), we could change it with:
```UnsatisfiableAction: ScheduleAnyway```
whose default value was `DoNotSchedule`

I think we should have improved this in docs on this :slightly_smiling_face:

So just to confirm then, I can safely disable the scheduler without losing any critical functionality?

By `disable the scheduler` do you mean `UnsatisfiableAction: ScheduleAnyway` ?

I mean `scheduler.create = false` so it doesn’t create any scheduler pods

<@U03KDNFSZ24> yes, it’s totally safe as by default schedulerName is not `nebula-scheduler` it’s actually not used.