Begin here if your machine is Windows or Intel Mac. For these machines, we use VirtualBox as the hypervisor, and Vagrant to provision the Virtual Machines.
This should also work with Linux (as the host operating system, not running in a VM), but it not so far tested.
This lab provisions 5 VMs on your workstation. That's a lot of compute resource!
- 16GB RAM. It may work with less, but will be slow and may crash unexpectedly.
- 8 core or better CPU e.g. Intel Core-i7/Core-i9, AMD Ryzen-7/Ryzen-9. May work with fewer, but will be slow and may crash unexpectedly.
- 50 GB disk space
Download and install VirtualBox on any one of the supported platforms:
- Windows
- Intel Mac
- Linux
Once VirtualBox is installed you may chose to deploy virtual machines manually on it. Vagrant provides an easier way to deploy multiple virtual machines on VirtualBox more consistently.
Download and install Vagrant on your platform.
- Windows
- Debian/Ubuntu
- CentOS
- Linux
- Intel Mac
This tutorial assumes that you have also installed Vagrant.
The labs have been configured with the following networking defaults. It is not recommended to change these. If you change any of these after you have deployed any of the lab, you'll need to completely reset it and start again from the beginning:
vagrant destroy -f
vagrant upIf you do change any of these, please consider that a personal preference and don't submit a PR for it.
The network used by the VirtualBox virtual machines is 192.168.56.0/24.
To change this, edit the Vagrantfile in your cloned copy (do not edit directly in github), and set the new value for the network prefix at line 9. This should not overlap any of the other network settings.
Note that you do not need to edit any of the other scripts to make the above change. It is all managed by shell variable computations based on the assigned VM IP addresses and the values in the hosts file (also computed).
It is recommended that you leave the pod and service networks with the following defaults. If you change them then you will also need to edit one or both of the CoreDNS and Weave networking manifests to accommodate your change.
The network used to assign IP addresses to pods is 10.244.0.0/16.
To change this, open all the .md files in the docs directory in your favourite IDE and do a global replace on
POD_CIDR=10.244.0.0/16
with the new CDIR range. This should not overlap any of the other network settings.
The network used to assign IP addresses to Cluster IP services is 10.96.0.0/16.
To change this, open all the .md files in the docs directory in your favourite IDE and do a global replace on
SERVICE_CIDR=10.96.0.0/16
with the new CDIR range. This should not overlap any of the other network settings.
Additionally edit line 164 of coredns.yaml to set the new DNS service address (should still end with .10)
tmux can be used to run commands on multiple compute instances at the same time. Labs in this tutorial may require running the same commands across multiple compute instances, in those cases consider using tmux and splitting a window into multiple panes with synchronize-panes enabled to speed up the provisioning process.
The use of tmux is optional and not required to complete this tutorial.
Enable synchronize-panes by pressing
CTRL+Bfollowed by"to split the window into two panes. In each pane (selectable with mouse), ssh to the host(s) you will be working with.
Next typeCTRL+Xat the prompt to begin sync. In sync mode, the dividing line between panes will be red. Everything you type or paste in one pane will be echoed in the other.
To disable synchronization typeCTRL+Xagain.
Note that theCTRL-Xkey binding is provided by a.tmux.confloaded onto the VM by the vagrant provisioner.
Next: Compute Resources