After Cert expires, ovnkube-master starts to log the below error as per our grpc loglevel this is actually a x509, I also confirmed a successful tcp conection was established and torndown in <100ms, https://github.com/grpc/grpc-go/issues/2561

egressip_healthcheck.go:162] Could not connect to $hostname ($ip:9107):context deadline exceeded

Rotate the openshift-ovn-kubernetes/ovn-cert and Wait for the old cert to expire

    1. wait %10 days after ovn-cert rotation, and with no pod restarts.
    2. After cert rotation, 18days (%10 of validity) egressIPs will be removed from all nodes.
    3. all nodes will start to fail egress health probes with context deadline exceeded
    

Silent failure of egressIP healthchecks 

    No noticable impact, automatic loading of new cert/restart of pod

    whom ever rotated the cert should be restarting the daemonsets. and we should also log x509 issues in the grpc library.