Bug Report

What did you do?
The operator pod was preempted from the cluster to allow other high priority pod.

What did you expect to see?
The operator pod was rescheduled and it should become the leader.

What did you see instead? Under which circumstances?
The new operator pod started did not become the leader instead it was waiting as previous preempted pod is still the leader.

Environment

• operator-lib version: v0.12.0

Possible Solution
check for pod preemption along with the eviction

Additional context
Add any other context about the problem here.