Update virtualbox build

docs/11-Install-Kubernetes-the-kubeadm-way/03-Provision-VMs-with-Vagrant.md

@@ -2,4 +2,8 @@
 
   - Take me to [Lecture](https://kodekloud.com/topic/deploy-with-kubeadm-provision-vms-with-vagrant/)
 
-If you have an Apple M1 or M2 (Apple Silicon) machine, then please follow the separate instructions [here](../../apple-silicon/README.md).
+If you want to build your own cluster, check these out. They are more up to date than the video currently :smile:
+
+* [Kubeadm Clusters](../../kubeadm-clusters/)
+* [Managed Clusters](../../managed-clusters/)
+

kubeadm-clusters/README.md

@@ -13,3 +13,10 @@ In this section we present various labs for building kubeadm clusters
     For users of Mac M1/M2, this is a lab that provisions a 2 or 3 node cluster (depending on how much memory your Mac has) using [Multipass](https://multipass.run/).
 
     * [2/3 Node Cluster](./apple-silicon/)
+
+* Vagrant and VirtualBox
+
+    For users of Windows and Mac x86, privsio a 3 node cluster on your laptop.
+
+    * [3 Node Cluster](./virtualbox/)
+

kubeadm-clusters/virtualbox/Vagrantfile

@@ -0,0 +1,87 @@
+# -*- mode: ruby -*-
+# vi:set ft=ruby sw=2 ts=2 sts=2:
+
+# Define the number of master and worker nodes
+# If this number is changed, remember to update setup-hosts.sh script with the new hosts IP details in /etc/hosts of each VM.
+NUM_WORKER_NODE = 2
+
+IP_NW = "192.168.56."
+MASTER_IP_START = 10
+NODE_IP_START = 20
+
+# Sets up hosts file and DNS
+def setup_dns(node)
+  # Set up /etc/hosts
+  node.vm.provision "setup-hosts", :type => "shell", :path => "ubuntu/vagrant/setup-hosts.sh" do |s|
+    s.args = ["enp0s8", node.vm.hostname]
+  end
+  # Set up DNS resolution
+  node.vm.provision "setup-dns", type: "shell", :path => "ubuntu/update-dns.sh"
+end
+
+# Runs provisioning steps that are required by masters and workers
+def provision_kubernetes_node(node)
+  # Set up kernel parameters, modules and tunables
+  # node.vm.provision "setup-kernel", :type => "shell", :path => "ubuntu/setup-kernel.sh"
+  # Restart
+  #   node.vm.provision :shell do |shell|
+  #     shell.privileged = true
+  #     shell.inline = "echo Rebooting"
+  #     shell.reboot = true
+  #   end
+  # Set up DNS
+  setup_dns node
+end
+
+# All Vagrant configuration is done below. The "2" in Vagrant.configure
+# configures the configuration version (we support older styles for
+# backwards compatibility). Please don't change it unless you know what
+# you're doing.
+Vagrant.configure("2") do |config|
+  # The most common configuration options are documented and commented below.
+  # For a complete reference, please see the online documentation at
+  # https://docs.vagrantup.com.
+
+  # Every Vagrant development environment requires a box. You can search for
+  # boxes at https://vagrantcloud.com/search.
+  # config.vm.box = "base"
+  config.vm.box = "ubuntu/jammy64"
+  config.vm.boot_timeout = 900
+
+  # Disable automatic box update checking. If you disable this, then
+  # boxes will only be checked for updates when the user runs
+  # `vagrant box outdated`. This is not recommended.
+  config.vm.box_check_update = false
+
+  # Provision Master Nodes
+  config.vm.define "kubemaster" do |node|
+    # Name shown in the GUI
+    node.vm.provider "virtualbox" do |vb|
+      vb.name = "kubemaster"
+      vb.memory = 2048
+      vb.cpus = 2
+    end
+    node.vm.hostname = "kubemaster"
+    node.vm.network :private_network, ip: IP_NW + "#{MASTER_IP_START}"
+    node.vm.network "forwarded_port", guest: 22, host: "#{2710}"
+    provision_kubernetes_node node
+    # Install (opinionated) configs for vim and tmux on master-1. These used by the author for CKA exam.
+    node.vm.provision "file", source: "./ubuntu/tmux.conf", destination: "$HOME/.tmux.conf"
+    node.vm.provision "file", source: "./ubuntu/vimrc", destination: "$HOME/.vimrc"
+  end
+
+  # Provision Worker Nodes
+  (1..NUM_WORKER_NODE).each do |i|
+    config.vm.define "kubenode0#{i}" do |node|
+      node.vm.provider "virtualbox" do |vb|
+        vb.name = "kubenode0#{i}"
+        vb.memory = 1024
+        vb.cpus = 1
+      end
+      node.vm.hostname = "kubenode0#{i}"
+      node.vm.network :private_network, ip: IP_NW + "#{NODE_IP_START + i}"
+      node.vm.network "forwarded_port", guest: 22, host: "#{2720 + i}"
+      provision_kubernetes_node node
+    end
+  end
+end

kubeadm-clusters/virtualbox/docs/01-prerequisites.md

@@ -0,0 +1,96 @@
+# Prerequisites
+
+If you have an M-series (Apple Silicon) Mac, you cannot run VirtualBox. Please instead see our [Apple Silicon](../../apple-silicon/) guide.
+
+## VM Hardware Requirements
+
+8 GB of RAM
+50 GB Disk space
+
+## Virtual Box
+
+Download and Install [VirtualBox](https://www.virtualbox.org/wiki/Downloads) on any one of the supported platforms:
+
+ - Windows hosts
+ - OS X hosts (x86 only, not M1)
+ - Linux distributions
+ - Solaris hosts
+
+## Vagrant
+
+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](https://www.vagrantup.com/) on your platform.
+
+- Windows
+- Debian
+- Centos
+- Linux
+- macOS (x86 only, not M1)
+
+This tutorial assumes that you have also installed Vagrant.
+
+
+## Lab Defaults
+
+The labs have been configured with the following networking defaults. 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:
+
+```bash
+vagrant destroy -f
+vagrant up
+```
+
+If you do change any of these, **please consider that a personal preference and don't submit a PR for it**.
+
+### Virtual Machine Network
+
+The network used by the Virtual Box virtual machines is `192.168.56.0/24`.
+
+To change this, edit the [Vagrantfile](../vagrant/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 the Weave networking manifests to accommodate your change.
+
+If you do decide to change any of these, please treat as personal preference and do not raise a pull request.
+
+### NAT Networking
+
+Due to how VirtualBox/Vagrant works, the networking for each VM requires two network adapters; one NAT (`enp0s3`) to communicate with the outside world, and one internal (`enp0s8`) which is attached to the VirtualBox network mentioned above. By default, Kubernetes components will connect to the default network adapter - the NAT one, which is *not* what we want, therefore there is a bit of extra configuration required to get around this, which you will encounter in the coming lab sections.
+
+We have pre-set an environment variable `INTERNAL_IP` on all VMs which is the IP address that kube components should be using. For those interested, this variable is assigned the result of the following command
+
+```bash
+ip -4 addr show enp0s8 | grep "inet" | head -1 | awk '{print $2}' | cut -d/ -f1
+```
+
+### Pod Network
+
+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](../docs/) directory in your favourite IDE and do a global replace on<br>
+`POD_CIDR=10.244.0.0/16`<br>
+with the new CDIR range.  This should not overlap any of the other network settings.
+
+### Service Network
+
+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](../docs/) directory in your favourite IDE and do a global replace on<br>
+`SERVICE_CIDR=10.96.0.0/16`<br>
+with the new CDIR range.  This should not overlap any of the other network settings.
+
+## Running Commands in Parallel with tmux
+
+[tmux](https://github.com/tmux/tmux/wiki) can be used to run the same 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 you may consider using tmux and splitting a window into multiple panes with synchronize-panes enabled to speed up the provisioning process.
+
+In order to use tmux, you must first connect to `kubemaster` and run tmux there. From inside the tmux session you can open multiple panes and ssh to the worker nodes from these panes.
+
+> The use of tmux is optional and not required to complete this tutorial.
+
+![tmux screenshot](../../../images/tmux-screenshot.png)
+
+> Enable synchronize-panes by pressing `CTRL+B` followed by `"` to split the window into two panes. In each pane (selectable with mouse), ssh to the host(s) you will be working with.</br>Next type `CTRL+X` at 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.<br>To disable synchronization type `CTRL+X` again.</br></br>Note that the `CTRL-X` key binding is provided by a `.tmux.conf` loaded onto the VM by the vagrant provisioner.<br/>To paste commands into a tmux pane, use `SHIFT-RightMouseButton`.
+
+Next: [Compute Resources](02-compute-resources.md)