Comment 7 for bug 1922578

Weirdly, I'm not able to reproduce the sigterm timeout when I remove kubeapi-load-balancer from the deployment. This is making it quite difficult to reproduce the original problem since I need to run hacluster instead of kubeapi-load-balancer to reproduce the pacemaker part of the issue.

I'm going to mark this as incomplete for now since we don't have enough info to act on this report. We'll need either clear reproduction steps, or more detailed log output from pacemaker during a failure event, to figure out what's really going on here.