Lab2.2 - Worker node not starting

mikelmaas

I'm using AWS EC2 instances with ubuntu version 24.04 for cp and worker nodes. CP node is started properly. Note: I can't select ubuntu 20.x on AWS, 22.x is the oldest.

The join command on the worker node doesn't work. When I check the node (kubectl get nodes) I get the following message:

E1118 16:20:38.157848 10649 memcache.go:265] "Unhandled Error" err="couldn't get current server API group list: Get \"http://localhost:8080/api?timeout=32s\": dial tcp 127.0.0.1:8080: connect: connection refused"

Please advise what todo. There are no files in the $HOME/.kube directory.

mikelmaas

Can I use minikube to perform all the labs as an alternative?

chrispokorni

Hi @mikelmaas,

The join command on the worker node doesn't work

Do you see any errors when running the join command? Please share them to help with troubleshooting.

When I check the node (kubectl get nodes) ... There are no files in the $HOME/.kube directory.

Are you running the kubectl command on the cp node? The $HOME/.kube directory and its content are missing on the cp node?

Due to its automation and abstraction layers Minikube is not a recommended lab environment for this course. Several course exercises explore features that cannot be reproduced on Minikube.

Regards,
-Chris

mikelmaas

Hi Chris,

Thank you for your response. Attached are the logging of the worker script, and the output of some commands on the worker.

The cp node has a correct .kube dir and contents. Kubectl get nodes on the cp node shows a running cp node.

Best regards,
Mikel

mikelmaas

Note: the output of the worker logging is now based on the 22.04 Ubuntu version AWS offers. This is the oldest version which can be selected.

chrispokorni

Hi @mikelmaas,

With Ubuntu 20.04 LTS image only available as an AWS Marketplace AMI, picking the next available release from the Quick Start AMIs list makes sense. While Ubuntu 22.04 LTS has not been fully tested, it seems that 24.04 LTS works well for lab VMs.

The errors you see are the expected behavior when running the kubectl get nodes command on the worker node. The missing .kube is also expected. Perhaps reading though the exercise description will help to clarify this.

What happened after you executed the sudo kubeadm join command on the worker node? Does the node join the cluster? When provisioning the two EC2 instances, did you make sure to follow the video guide from the introductory chapter for VM configuration and SG rules?

Regards,
-Chris

mikelmaas

Hi Chris,

Thank you for your support, it is now working properly on 24.04. I didn't configure the security group properly, my bad. Apologies for wasting your time. I'm glad I can continue with the course now.

Best regards,
Mikel