Vagrantfile and Scripts to Automate Kubernetes Setup using Kubeadm [Practice Environment for CKA/CKAD and CKS Exams]

A fully automated setup for CKA, CKAD, and CKS practice labs is tested on the following systems:

• Windows
• Ubuntu Desktop
• Mac Intel-based systems

If you are MAC Silicon user, Please use the follwing repo.

• Vagrant Kubeadm Setup on MAC Silicon

CKA, CKAD, CKS, or KCNA Vouchers Codes

As part of our commitment to helping the DevOps community save money on Kubernetes Certifications, we continuously update the latest voucher codes from the Linux Foundation

🚀 CKA, CKAD, CKS, or KCNA exam aspirants can save $100 today using code EARTHDAY24COM at https://kube.promo/devops. It is a limited-time offer from the Linux Foundation.

The following are the best bundles to save up to $419 with code EARTHDAY24COM

• CKA + CKAD + CKS Exam bundle ($419 Savings): kube.promo/k8s-bundle
• CKA + CKS Bundle ($283 Savings) kube.promo/bundle
• KCNA + CKA ( $229 Savings) kube.promo/kcka-bundle
• KCSA + CKS Exam Bundle ($229 Savings) kube.promo/kcsa-cks
• KCNA + KCSA Exam Bundle ($203 Savings) kube.promo/kcna-kcsa

Note: You have one year of validity to appear for the certification exam after registration

Setup Prerequisites

• A working Vagrant setup using Vagrant with VirtualBox or libvirt available
• If using libvirt user needs to be added to libvirt group (sudo usermod -aG libvirt $(whoami))

Documentation

Current k8s version for CKA, CKAD, and CKS exam: 1.29.

The setup is updated with 1.29 cluster version.

Refer to this link for documentation full: https://devopscube.com/kubernetes-cluster-vagrant/

Prerequisites

1. Working Vagrant setup
2. 8 Gig + RAM workstation as the Vms use 3 vCPUS and 4+ GB RAM

Firewall Configuration

To allow virtual machines to access NFS server on the host machine you will probably need to update firewall rules.

Rules for VirtualBox

sudo firewall-cmd --permanent --new-zone=virtualbox \
  && sudo firewall-cmd --permanent --zone=virtualbox --add-interface=vboxnet0 \
  && sudo firewall-cmd --permanent --zone=virtualbox --add-interface=vboxnet1 \
  && sudo firewall-cmd --permanent --zone=virtualbox --add-service=nfs3 \
  && sudo firewall-cmd --permanent --zone=virtualbox --add-service=nfs \
  && sudo firewall-cmd --permanent --zone=virtualbox --add-service=rpc-bind \
  && sudo firewall-cmd --permanent --zone=virtualbox --add-service=mountd \
  && sudo firewall-cmd --reload

Rules for libvirt

sudo firewall-cmd --permanent --zone=libvirt --add-service=nfs3 \
  && sudo firewall-cmd --permanent --zone=libvirt --add-service=nfs \
  && sudo firewall-cmd --permanent --zone=libvirt --add-service=rpc-bind \
  && sudo firewall-cmd --permanent --zone=libvirt --add-service=mountd \
  && sudo firewall-cmd --reload

For MAC/Linux Users with VirtualBox

The latest version of Virtualbox for Mac/Linux can cause issues.

Create/edit the /etc/vbox/networks.conf file and add the following to avoid any network-related issues.

* 0.0.0.0/0 ::/0

or run below commands

sudo mkdir -p /etc/vbox/
echo "* 0.0.0.0/0 ::/0" | sudo tee -a /etc/vbox/networks.conf

So that the host only networks can be in any range, not just 192.168.56.0/21 as described here: https://discuss.hashicorp.com/t/vagrant-2-2-18-osx-11-6-cannot-create-private-network/30984/23

Bring Up the Cluster

To provision the cluster, execute the following commands.

git clone https://github.com/scriptcamp/vagrant-kubeadm-kubernetes.git
cd vagrant-kubeadm-kubernetes
cp settings.yaml.sample settings.yaml

With VirtualBox

vagrant up --provider virtualbox

With libvirt

vagrant up --provider libvirt

Set Kubeconfig file variable

cd vagrant-kubeadm-kubernetes

export KUBECONFIG=$(pwd)/configs/config

or you can copy the config file to .kube directory.

cp configs/config ~/.kube/

Install Kubernetes Dashboard

The dashboard is automatically installed by default, but it can be skipped by commenting out the dashboard version in settings.yaml before running vagrant up.

If you skip the dashboard installation, you can deploy it later by enabling it in settings.yaml and running the following:

vagrant ssh -c "/vagrant/scripts/dashboard.sh" controlplane

Kubernetes Dashboard Access

To get the login token, copy it from config/token or run the following command:

kubectl -n kubernetes-dashboard get secret/admin-user -o go-template="{{.data.token | base64decode}}"

Make the dashboard accessible:

kubectl proxy

Open the site in your browser:

http://localhost:8001/api/v1/namespaces/kubernetes-dashboard/services/https:kubernetes-dashboard:/proxy/#/login

To shutdown the cluster,

vagrant halt

To restart the cluster,

vagrant up

To destroy the cluster,

vagrant destroy -f