Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to join worker nodes to the cluster: error execution phase preflight: couldn't validate the identity of the API Server #16

Open
cmartinio opened this issue Apr 26, 2023 · 3 comments

Comments

@cmartinio
Copy link

I am getting an error in the setup stage (preflight check) no route to host. After running it with --v to check the stacktrace, I see the message saying: [discovery] Failed to request cluster-info, will try again: Get

@lovemasta41
Copy link

How did you run kubeadm init ? With or without pod cidr ? My calico pods are not even starting it’s in crashloopbackoff state? Did you face same issue ?

@lovemasta41
Copy link

Follow the simple method and check my issue.

@zenlinux121
Copy link

I faced the same error when using Virtualbox after setting up the VMs using Ubuntu 22.04 LTS as described in the PDF. The error was fixed when I changed the Network card type from NAT to bridge and with fixed IP addresses to avoid changes from DHCP. The error happened because the communication between VMs was not possible, except port 22, when NAT is type is set. After changing the network adapter to bridge type and starting from zero the procedure to install vanilla Kubernetes everything worked as expected.
Also I tried adding another network adapter but it failed as well because the TLS certificate is only applied to one network adapter when doing kubeadm init. I guess there is an option to generate the TLS certificate to all network adapters for kubeadm init.

Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants