Powering off a recently deployed 4.19.9 cluster using Assisted Installer for 24h or more, breaks the cluster. Bootstraper CSR are created but once they are approved, KAS stopped trusting the kubelet-client certificates rendering the cluster unusable. 

4.19.19

Deploying a fresh 4.19.9 multi node cluster using assisted installer. Once the cluster is deployed, power off. After 24h or more, bring the cluster up again. 

    1. Create a basic multi node cluster using 4.19.9 version.
    2. Wait for the cluster to be deployed and power nodes off.
    3. After 24h or more, bring up the cluster

Symptoms are the following:
- Csr are created right away but not approved (all nodes).
- After approving all the Pending CSR, contact is lost with the cluster. No oc logs, oc rsh since it throws tls error. 
- KAS starts to reject connections from kubelet since it doesn't trust kubelet certificate anymore. For this reason kubelet-server-current.pem csr is never issued. 
- Cluster stops working.
    

Cluster stops working.

Cluster should be working with no issues.