This repository tries to automate the guide "Kubernetes The Hard Way" by Kelsey Hightower, using Vagrant and Virtualbox.

• Vagrant
• VirtualBox 5.2
• kubectl
• cfssl
• cfssljson

Find my attempt at documenting this here Documentation

PKI and TLS Tools by Cloudflare (https://github.com/cloudflare/cfssl)

For Linux :
 curl -o /usr/local/bin/cfssl https://pkg.cfssl.org/R1.2/cfssl_linux-amd64
 curl -o /usr/local/bin/cfssljson https://pkg.cfssl.org/R1.2/cfssljson_linux-amd64
 chmod +x /usr/local/bin/cfssl*

For Mac :
 curl -o /usr/local/bin/cfssl https://pkg.cfssl.org/R1.2/cfssl_darwin-amd64
 curl -o /usr/local/bin/cfssljson https://pkg.cfssl.org/R1.2/cfssljson_darwin-amd64
 chmod +x /usr/local/bin/cfssl*

For Windows :
  Download https://pkg.cfssl.org/R1.2/cfssl_windows-amd64.exe
  Download https://pkg.cfssl.org/R1.2/cfssljson_windows-amd64.exe
  Do whatever Windows people do

First off, edit the file config. Here you can specify how many of each type of nodes you want. Eg. 3 master nodes. Also you can specify the number of CPU and Memory for each type.

Once thats done, just run ./install.sh.

The script set the number of nodes you want and the resources they get. It then generates a hosts file with ip's and hostnames. This is used to configure each node in the cluster. Then it generates certificates, based on the hostfile.

Now it calls Vagrant to provition the nodes. While provitioning the nodes, Vagrant will copy scripts and certifiates to each node and execute them. The script can be found under the scripts folder and the certificates under the folder ssl.

kubectl config use-context kubernetes-the-easy-way

kubectl get nodes

Because we trick Vagrant into being dynamic in regards to number of machines, we need to set our variables before we can use Vagrant commands. So in order to use Vagrant commands, after the install.sh script has finished, run this

source config
vagrant ssh k8s-worker-1

If Kubernetes is not your thing after all, or that you for other reasons want to remove the cluster, simply run this script

./destroy.sh

Remember to run the destroy.sh script before running the install.sh script again.