Looks like yet another case where pacemaker (hacluster), which hijacks control of the systemd services, has decided not to restart kube-apiserver. Yay.
kube-apiserver stopped at 03:11:35, no restart attempted for the next ~4 hours.
I could have sworn there is an open issue about this, but I can't find it.
Looks like yet another case where pacemaker (hacluster), which hijacks control of the systemd services, has decided not to restart kube-apiserver. Yay.
kube-apiserver stopped at 03:11:35, no restart attempted for the next ~4 hours.
I could have sworn there is an open issue about this, but I can't find it.