[discovery] Failed to connect to API Server "172.30.250.79:6443": token id "kakyg6" is invalid for this cluster or it has expired. Use "kubeadm token create" on the master node to creating a new valid token

[discovery] Failed to connect to API Server "172.30.250.79:6443": token id "kakyg6" is invalid for this cluster or it has expired. Use "kubeadm token create" on the master node to creating a new valid token

[discovery] Failed to connect to API Server "172.30.250.79:6443": token id "kakyg6" is invalid for this cluster or it has expired. Use "kubeadm token create" on the master node to creating a new valid token

[discovery] Failed to connect to API Server "172.30.250.79:6443": token id "kakyg6" is invalid for this cluster or it has expired. Use "kubeadm token create" on the master node to creating a new valid token

[discovery] Failed to connect to API Server "172.30.250.79:6443": token id "kakyg6" is invalid for this cluster or it has expired. Use "kubeadm token create" on the master node to creating a new valid token

[discovery] Failed to connect to API Server "172.30.250.79:6443": token id "kakyg6" is invalid for this cluster or it has expired. Use "kubeadm token create" on the master node to creating a new valid token

[discovery] Failed to connect to API Server "172.30.250.79:6443": token id "kakyg6" is invalid for this cluster or it has expired. Use "kubeadm token create" on the master node to creating a new valid token

[discovery] Failed to connect to API Server "172.30.250.79:6443": token id "kakyg6" is invalid for this cluster or it has expired. Use "kubeadm token create" on the master node to creating a new valid token

[discovery] Failed to connect to API Server "172.30.250.79:6443": token id "kakyg6" is invalid for this cluster or it has expired. Use "kubeadm token create" on the master node to creating a new valid token

[discovery] Failed to connect to API Server "172.30.250.79:6443": token id "kakyg6" is invalid for this cluster or it has expired. Use "kubeadm token create" on the master node to creating a new valid token

[discovery] Failed to connect to API Server "172.30.250.79:6443": token id "kakyg6" is invalid for this cluster or it has expired. Use "kubeadm token create" on the master node to creating a new valid token

[discovery] Failed to connect to API Server "172.30.250.79:6443": token id "kakyg6" is invalid for this cluster or it has expired. Use "kubeadm token create" on the master node to creating a new valid token

[discovery] Failed to connect to API Server "172.30.250.79:6443": token id "kakyg6" is invalid for this cluster or it has expired. Use "kubeadm token create" on the master node to creating a new valid token

[discovery] Failed to connect to API Server "172.30.250.79:6443": token id "kakyg6" is invalid for this cluster or it has expired. Use "kubeadm token create" on the master node to creating a new valid token

[discovery] Failed to connect to API Server "172.30.250.79:6443": token id "kakyg6" is invalid for this cluster or it has expired. Use "kubeadm token create" on the master node to creating a new valid token

[discovery] Failed to connect to API Server "172.30.250.79:6443": token id "kakyg6" is invalid for this cluster or it has expired. Use "kubeadm token create" on the master node to creating a new valid token

[discovery] abort connecting to API servers after timeout of 5m0s

couldn't validate the identity of the API Server: abort connecting to API servers after timeout of 5m0

Hey, seems like your token has expired, why don't you try creating another token for master?

[discovery] Failed to connect to API Server "172.30.250.79:6443": token id "kakyg6" is invalid for this cluster or it has expired. Use "kubeadm token create" on the master node to creating a new valid token

Also, you're getting the following error because you've already executed the join command on your nodes. Its created your /etc/kubernetes/pki/ca.crt file even though your node failed to join.

To get rid of this error, execute the following reset command on your node and execute then join command again. This will reset your cluster environment and then when you try joining the node again to the cluster, it will create all the files again.