I was wondering what scheduler pods did in nebula-operator. There doesn’t seem to be any documentation on it that I could find

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 see!

By

disable the scheduler

do you mean

UnsatisfiableAction: ScheduleAnyway

?

I mean

scheduler.create = false

so it doesn’t create any scheduler pods

@Jeremy Simpson yes, it’s totally safe as by default schedulerName is not

nebula-scheduler

it’s actually not used.

great, thank you