Sanity Check on Lab 3.1-10

Hello,

It may be easier to configure VirtualBox to configure a different IP address, but if if you did properly change Calico and the kubeadm-config.yaml file to use the new IP it should work. As with many things in a dynamic, open source project testing is the only way to know as there may be some new or lesser known setting which may at some point conflict.

Regards,

Hi kingveder,

I ran into similar problem with VirtualBox. I opted for a slightly more complex setup but ultimately made things easier since I don't have to customize anything. I created a group of k8s vms and attached their NICs to "Internal Network" which allows me to use any IP address scheme but then these are completely isolated from the host and the rest of the world. To solve that, I created a VM running Endian's community firewall https://www.endian.com/community/ which is bridged to the network and also attached to the same Internal Network as the k8s VMs and this allows me to access the VMs from SSH, etc and they can access the internet as well.

Hi @kingveder,

I have been provisioning VirtualBox VMs for Kubernetes clusters with a single bridged network adapter attached to each machine, supporting the Kubernetes required VM to VM networking and the VM to internet connectivity.

Regards,
-Chris