Page 9: Bootstrapping the Kubernetes Worker Nodes
We’ll need a new tmux session with panes for each worker, similar to the one we used to configure the controllers.
We’ll follow all of the source tutorial, with a one exception, setting the POD_CIDR value on each worker:
POD_CIDR=$(cat /run/cloud-init/instance-data.json | python3 -c 'import sys, json; print(json.load(sys.stdin)["ds"]["meta_data"]["pod-cidr"])')
If you are using your own IP address ranges, you will need to make some additional changes.
Once this part is done, you can close the worker tmux session.
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