<p>While joining the centos 7 node to cluster 1.9.0, <code>kubeadm join</code> command gives this error message.</p>
<p><code>Failed to request cluster info, will try again: [Get https://10.10.10.10:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: x509: certificate has expired or is not yet valid]</code></p>
<p>I got this message last night, this morning when run this command it worked.  I removed and trying to create the cluster this morning, again its giving same error message.</p>
<pre><code>kubeadm join --token f115fe.f0eea05182abe63a 10.10.10.10:6443 --discovery-token-ca-cert-hash sha256:48d4dc90a08ff73a0cfc63e30a313aaf1903fd51da8f9ce4cc79f95ce529b8d1

[discovery] Created cluster-info discovery client, requesting info from &quot;https://10.10.10.10:6443&quot;
[discovery] Requesting info from &quot;https://10.10.10.10:6443&quot; again to validate TLS against the pinned public key
[discovery] Failed to request cluster info, will try again: [Get https://10.10.10.10:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: x509: certificate has expired or is not yet valid]
[discovery] Failed to request cluster info, will try again: [Get https://10.10.10.10:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: x509: certificate has expired or is not yet valid]
</code></pre>
<p>How to resolve this error message?</p>

sfgroups
<p>The root cause of the issue is my node didn't have the correct time. after configuring NTP service node was able to join the master.</p>
