Adventures in Freebernetes Tutorial: Build Your Own Bare-VM Kubernetes Cluster the Hard Way

Page 5: Generating Kubernetes Configuration Files for Authentication

You only need to make two changes to this section: at the very beginning, set KUBERNETES_PUBLIC_ADDRESS= instead of using the gcloud command shown, and at the very end when copying files to the VMs. Otherwise, follow the rest of the steps in the original.

for instance in worker-0 worker-1 worker-2; do
scp -i ~cbsd/.ssh/id_rsa -oStrictHostKeyChecking=no ${instance}.kubeconfig kube-proxy.kubeconfig ubuntu@${instance}:~/
for instance in controller-0 controller-1 controller-2; do
scp -i ~cbsd/.ssh/id_rsa -oStrictHostKeyChecking=no admin.kubeconfig kube-controller-manager.kubeconfig \
kube-scheduler.kubeconfig ubuntu@${instance}:~/
view raw hosted with ❤ by GitHub

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14

3 thoughts on “Adventures in Freebernetes Tutorial: Build Your Own Bare-VM Kubernetes Cluster the Hard Way

Add yours

  1. 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 ? )


    1. It is actually using a CNI plugin ( 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.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

Blog at

Up ↑

%d bloggers like this: