Page 7: Bootstrapping the etcd Cluster
For this section, use ssh -i ~cbsd/.ssh/id_rsa ... instead of the gcloud command to log in to the controllers.
Replace the INTERNAL_IP setter:
INTERNAL_IP=$(dig @10.0.0.1 +short `hostname`.hardk8s.local)
If you are using your own IP address ranges, you will need to make some additional changes.
After that, all commands are executed on each of the controllers. As the tutorial recommends, using tmux synchronization makes this section much easier.
If you’re on a slow Internet connection, you may also want to download the tarball once and copy it from your FreeBSD host to the controller VMs.
The commands on the next page also need to be executed on each controller, so you can leave your tmux session open.
Running In Production With Scissors 
What a fantastic and interesting job you’ve done! I will definitely try!
Question – as far as I understand, you are not using any K8S CNI ( calico, flannel, … ). How your cluster works with multiple nodes ( ip address for pod, connectivity ? )
LikeLike
It is actually using a CNI plugin (https://github.com/containernetworking/plugins) although it just creates a basic bridge for the container network. Most CNI plugins should work fine on this cluster, which does actually have three worker nodes, and I’ve tested pod connectivity between nodes. A simple test for full CNI functionality would be to install Calico and test a NetworkPolicy.
LikeLike