KS need to gracefully terminate so the next replica can take over during a rollout. Graceful termination is important for giving up the lease, so another replica can become the leader without waiting 60s for the lease to expire.
When update scheduler operator cluster or delete the static pod yaml file from master node ,we could see logs like : I0922 02:45:38.708205 1 server.go:207] Requested to terminate. Exiting. and the other pods acquired the lead less than 20S.
lease duration 15s, renew deadline 10s - so it should be shortly after 10s
Confirmed with 4.6.0-0.nightly-2020-09-25-085318, the issue has fixed: the KS will renew lead within 10s . I0925 13:41:45.177618 1 server.go:207] Requested to terminate. Exiting. I0925 13:41:45.747402 1 leaderelection.go:253] successfully acquired lease openshift-kube-scheduler/kube-scheduler. I0925 13:45:11.188109 1 server.go:207] Requested to terminate. Exiting. I0925 13:45:11.243587 1 leaderelection.go:253] successfully acquired lease openshift-kube-scheduler/kube-scheduler
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.6 GA Images), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4196