VirtualBox Help when trying to join the worker node to the master node.
Hi,
I'm know I have the token and sha value right for the master and it's IP address.
I remember seeing something about Promiscuous mode.
What are the recommended settings for this to work in virtualbox as there are many virtual networks that can be created.
It says my nodes can't see each other, but I can ping them from each other. I'm using NAT right now.
Comments
-
Hi,
This is a solution I posted about a year ago, and it is not revised for newer versions of VirtualBox and Kubernetes or VM sizes. Make sure you follow the latest lab version for recommended VM sizes. However, I believe the steps in general still apply today:
"......
vBox 5.2.8
1. Created 2 VMs, 2 GB each
2. Adapter 1 ONLY - Bridged interface on each (Allow All)
3. Installed Ubuntu 16 and vbox guest additions
4. ip a (or ifconfig) outputs showed different enp0s3 IPs for each Ubuntu instance: master 10.0.0.50 and second 10.0.0.125
5. ufw status -> inactive (I did not have to do anything here)
6. nc to test inter-node communication, messages were delivered successfully from master to second and second to master
7. swapoff -a
8. commented out swap in /etc/fstabAll steps in labs 3.1, 3.2, 3.3 completed successfully, except Lab 3.3 Step 6, where I was able to access the nginx page, from a browser on my Host machine, only on the
:32056, which in my case was 10.0.0.50:32056. With NAT only I was not able to get anywhere, because like you said, the VM instances were not able to communicate with each other.
......"Hope it helps,
-Chris
0 -
Chris,
So My home network is a 192.x network. I setup Calico following the direction on the 192.x network. Will this still work? I'm asking because if I bridge this to my host wifi card, it shows as a VM on my home network.
Thanks,
Bryan0 -
I remember reading about a similar scenario somewhere (stackoverflow, or somewhere else...) and the solution was to use a different network for calico. When doing so, before running
kubeadm init...first make sure you edit the calico.yaml file to change it there, and then the same network should be provided in thekubeadm init...command. This should resolve the conflicting/overlapping networks.
-Chris0 -
Hmmm. I might just move to the 10 network for now. Not like I have anything running in production...LOL.
0 -
Ugh, my router will not allow me to use anything other then 192.x...I feel like I'm fighting every step with this so far....
0 -
So Do I have to start over again since I don't know how to remove Calico and the Rbac thing?
0 -
I need help on Chapter 3 Step 9 on how to remove Calico and Rbac. I think I can edit Calico to use the 10 network, but I have no idea to to remove it. Help please.
0 -
Tried the reset as a last resort and seems to work. Edited the calico to move it to the 10.0.0.0/16 network. After that I got the worker node to join the cluster.
0 -
That was going to be my suggestion too. Glad it works now.
0 -
Yeah, you helped me get in the right direction. I feel this lab should really have dedicated sections to setups like Virtualbox because it is even mentioned as one of the ways you can take the class since they don't provide an actual cloud instance for us to use. I feel other people would get stuck here too.
0 -
So I ended up using Bridged Adapter. My home/lab network is on 192 so I had to edit calico to be on the 10 network. It was the only way I could get it to work. And no, it isn't documented anywhere....
0 -
Hi,
If you scroll up in this discussion thread you will find a solution I posted on how to setup vbox, it was April 8 and has about 8 steps in it. That configuration worked for me at the time when tested.
Regards,
-Chris0
Categories
- All Categories
- 177 LFX Mentorship
- 177 LFX Mentorship: Linux Kernel
- 750 Linux Foundation IT Professional Programs
- 373 Cloud Engineer IT Professional Program
- 169 Advanced Cloud Engineer IT Professional Program
- 74 DevOps IT Professional Program - Discontinued
- 4 DevOps & GitOps IT Professional Program
- 99 Cloud Native Developer IT Professional Program
- 7.6K Training Courses & Learning Paths
- 1 AI & ML Training
- 1 Blockchain & Decentralized Identity Training
- 3 Cloud & Containers Training
- 1 Cybersecurity Training
- 2 DevOps & Site-Reliability Training
- 1 Linux Kernel Development Training
- 1 Networking Training
- 1 Open Source Best Practice Training
- 1 System Administration Training
- 1 System Engineering Training
- 1 Web & Application Development Training
- 792 Hardware
- 202 Drivers
- 68 I/O Devices
- 37 Monitors
- 95 Multimedia
- 173 Networking
- 91 Printers & Scanners
- 87 Storage
- 769 Linux Distributions
- 81 Debian
- 68 Fedora
- 22 Linux Mint
- 13 Mageia
- 24 openSUSE
- 150 Red Hat Enterprise
- 31 Slackware
- 13 SUSE Enterprise
- 356 Ubuntu
- 465 Linux System Administration
- 31 Cloud Computing
- 73 Command Line/Scripting
- Github systems admin projects
- 98 Linux Security
- 78 Network Management
- 101 System Management
- 46 Web Management
- 106 Mobile Computing
- 18 Android
- 73 Development
- 1.2K New to Linux
- 1K Getting Started with Linux
- 392 Off Topic
- 121 Introductions
- 181 Small Talk
- 29 Study Material
- 955 Programming and Development
- 310 Kernel Development
- 627 Software Development
- 983 Software
- 375 Applications
- 182 Command Line
- 5 Compiling/Installing
- 68 Games
- 317 Installation
- Archived
- 2 LFD140 Class Forum
Upcoming Training
-
August 20, 2018
Kubernetes Administration (LFS458)
-
August 20, 2018
Linux System Administration (LFS301)
-
August 27, 2018
Open Source Virtualization (LFS462)
-
August 27, 2018
Linux Kernel Debugging and Security (LFD440)