Error execution phase preflight

Todd Gill

When joining my worker node to the control plane, I am getting the following error after it hangs for roughly 10 minutes:

[preflight] Running pre-flight checks
error execution phase preflight: couldn't validate the identity of the API Server: failed to request the cluster-info ConfigMap: client rate limiter Wait returned an error: rate: Wait(n=1) would exceed context deadline
To see the stack trace of this error execute with --v=5 or higher

This is the second attempt after deleting the instance and starting over.

How can I fix this?

chrispokorni

Hi @toddrickson,

Are your VMs fully seeing each other - is your cloud VPC firewall or local hypervisor allowing all ingress traffic to your VMs (from all sources, all protocols, to all port destinations)?

Is the control plane and worker node's hosts files correctly populated with the private IP address of the control plane VM and the expected k8scp alias (same entries in both hosts files)?

Are you extracting/selecting/copying the complete join command from the control plane node once it was generated?

Regards,
-Chris

Todd Gill

I looked at the /etc/hosts file and notice the IPs were not the same. I updated both VMs with the CP's private IP address with the k8scp alias.

I had another question before I retry this. for -node-name= ... since my worker name is : drogon-worker-20241121-045430 , do I need to put this name?

Thank you,

Todd

chrispokorni

Hi @toddrickson,

It is recommended to register the control plane node as 'cp' during init and the worker node as 'worker' during join. This will make things run much smoother in upcoming exercises.

Regards,
-Chris

Todd Gill

Nevermind, I ran it and it worked using the hostname mentioned above:

[preflight] Running pre-flight checks
[preflight] Reading configuration from the cluster...
[preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml'
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Starting the kubelet
[kubelet-check] Waiting for a healthy kubelet. This can take up to 4m0s
[kubelet-check] The kubelet is healthy after 1.003108567s
[kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap

This node has joined the cluster:

• Certificate signing request was sent to apiserver and a response was received.
• The Kubelet was informed of the new secure connection details.

Run 'kubectl get nodes' on the control-plane to see this node join the cluster.

Thank you! @chrispokorni