Lab 3.2 - cannot join worker node to cluster

josepmaria

Hello,

I have followed the instructions of Lab 3,1 and 3,2

I use 2 vm (ubuntu) to create the nodes, exactly like in the video. Each VM is sized 20MB, 2 nodes and 16GB of ram.

When trying to add the worker node (second vm) to the cp node (first vm), I obtain the following error:

I suspect this may be because when asking for the hostname on the cp node, I get 127.0.1.1.

Has anyone experienced a similar issue?

Thanks in advance for your help.

Josep Maria

josepmaria

Note: both VM have enabled nested virtualisation

chrispokorni

Hi @josepmaria,

The one thing I see so far is a typo, your join command is incorrect: it includes the backslash "\" (the multi-line separator) in what appears to be a single line command.

The hostname returning an unexpected IP address may be attributed to the type of network attached to the VM's network interface. For local VMs I recommend a single bridged network interface per VM. That will ensure the hypervisor uses DHCP to assign private IP addresses to your VMs.

As you configure each VM, ensure that their respective hosts files are properly populated with the private IP of the control plane node and the k8scp alias, as guided by steps in the lab guide.

Also, the "20MB" in your message, that seems to be inadequate. I recommend at least 20GB of virtual disk space per VM. Also 2 nodes (assuming CPU cores) should be enough, while 16GB RAM per VM may be slightly more than needed for the lab environment.

Regards,
-Chris

josepmaria

Hello @chrispokorni ,

Thanks for your answer.

As for single bridge network attached to my VM (vmware), I have the following options :

I have tried the options (wi-fi and autodetect) under Bridge Networking, and then restarted the VM. Unfortunately, when running the commnand $ hostname -i, it keep returning the same IP 127.0.1.1

Kindly let me knwo if there anything else I could go to obtain an expected IP when running $ hostname -i

Thanks for your time.

Sincerely,

Josep Maria

chrispokorni

Hi @josepmaria,

Perhaps viewing the output of the hostname --help command may reveal other options to list the IP addresses of your VM.

Another popular command is ip a but its output is much more complex.

Your hypervisor should have a DHCP option or a static IP assignment option to generate and assign private IP addresses to your VMs.

Regards,
-Chris

josepmaria

Hi @chrispokorni ,

Thank you for your answer. I appreciate it.

I shall do my best to find out a way to associate a private IP to the VM and let you know.

Sincerely,

Josep Maria