Hello guys, I've a question which could be silly, but I'm a little bit confused. . . .

Marco Tony:
Hello guys, I’ve a question which could be silly, but I’m a little bit confused.
We have --leader-elect=true to build the leader in case of same scheduler deployed on multiple musters.
Why we need --lock-object too?

AB:
–lock-object we use when we got multiple master. --leader-elect=true only for the one u want to be main master.

Marco Tony:
@AB So if I have multiple master I need to lock the name to be in synch

Marco Tony:
While if I have multiple master and I need to deploy the copy of this scheduler into those multiple master, I’ll elect only one as leader and leave the others as non-leader

Marco Tony:
Is that correct?

AB:
did you mean deploy custom scheduler as deployment ? or static pod?

AB:
Check this link
https://kubernetes.io/docs/tasks/extend-kubernetes/configure-multiple-schedulers/