Monday, October 22, 2018

Kubernetes cluster configuration in a Virtualbox with vagrant

Thanks to Rajkumar who had developed the Vagrantfile and published in the github on Kubernetes cluster configuration in a Virtualbox with vagrant. For those who don't know about Vagrant it is a tool that will be used for virtualization into a different level and more powerful way of using your system resources to run multiple operating virtual boxes in your Laptop/Desktop systems.

You just need to follow the simple steps which I had done in my experiment:

Prerequisites for Kubernetes Cluster Creation

  1. Download latest Vagrant
  2. Download latest version of Oracle VirtualBox
System resources requirements on VirtualBox

  • 2 GB for each node
  • 2 cores CPUs for each node
Here I have don this expeiment on my Windows 7 laptop. You could do same on any Windows higher version as well. Total 3 VMs will be created under a group named as - "Kubernetes Cluster" as defined in Vagrantfile.



Infrastructure as a Code: Vagrantfile 

The Vagrantfile will be composed with the Ruby array that creates k8s-head and k8s-node1, k8s-node2 definitions. Once the Ubuntu Xenial boxes provisioned custom shell scripts are used for boot time execution.


  • Both Master, Slave nodes common tasks are executed with the Shell provisioning inline options.
  • Install Docker CE 17.03
  • Added vagrant user to docker group to run docker commands as vagrant user (without using sudo for each not required)
  • Install the kubelet kubeadm kubectlk
  • kubelet requires swap off


You can do all the setups required to run the following in the sequence : 
  • k8s-master node runs on 192.168.33.10
  • k8s-slave1 node runs on 192.168.33.11
  • k8s-slave2 node runs on 192.168.33.12
Bootstrap Setup



Master node will be required the following steps
Slave node will be running and after bootup only runs inline joining the kubernetes cluster with a script generated in the master. node.

Executing the setup
vagrant up

check the VM are created as expected
vagrant status

Vagrant status of kuberenetes cluster
Check that all are in running state, if not you need to check the log file that is generated in the same path where Vagrantfile exists.

Connect with your PuTTY to k8s-master that is running on 192.168.33.10 IP address.

Check the versions of kubeadm, kubectl, and kubelet
  kubectl version
  kubeadm version
  # Better format output
  kubectl version -o yaml
  kubeadm version -o yaml
  

Kubeadm, kubectl, kubelet versions
Check the nodes list

kubectl get nodes

kubectl get nodes output

Note: Make sure that your Windows firewall disabled to run the Vagrant on your Windows laptop.

You might be more interested to explore and know about the latest Docker 19 Community Edition learning experiments on Ubuntu 19.04

References:

13 comments:

Unknown said...

This post , substantially updated to reflect the latest developments in the field of Kubernetes Cluster, introduces the concepts and best practices of software Kubernetes Cluster and how a Kubernetes Cluster system is structured and how that system's elements are meant to interact.

I just followed your procedure & with in 30 min , Kubernetes Cluster was opearional.


Infact , it's "A Practical Guide , Hands on tutorial Kubernetes Cluster" gives remarkable insider's story of Kubernetes.

Unknown said...

plz post minikube installation in oracle virtual box

Sai Elakiyaa said...





Great inspiration today!!! thanks for your blog.

android Training in Chennai
Python Training in Chennai
Best Spoken English Classes in Chennai
Java Training in Chennai
Spoken English Classes in Chennai
Spoken English in Chennai

Unknown said...

nice perfecto

Anonymous said...

thank you so much!!!

Unknown said...

I am unable to create a pod on ANY node because they have taints. ALL the Master and both the nodes have taints

vagrant@k8s-master:~$ kubectl describe no k8s-master | grep -i taint
Taints: node.kubernetes.io/not-ready:NoSchedule
vagrant@k8s-master:~$ kubectl describe no k8s-slave-1 | grep -i taint
Taints: node.kubernetes.io/not-ready:NoSchedule
vagrant@k8s-master:~$ kubectl describe no k8s-slave-2 | grep -i taint
Taints: node.kubernetes.io/not-ready:NoSchedule
vagrant@k8s-master:~$

DevOps said...

Nice blog. You have provided such a useful information in this blog. Thanks for sharing.
Docker and Kubernetes Training
Kubernetes Online Training
Docker Online Training

Unknown said...

Hi, I have the same issue . Can anyone post a solution for the problem?

ram said...

great content great blog thank u so much oracle training in chennai

sharath said...

the status is still not ready
NAME STATUS ROLES AGE VERSION
k8s-master NotReady master 41m v1.19.2
k8s-slave-1 NotReady 30m v1.19.2
k8s-slave-2 NotReady 22m v1.19.2
How can this be fixed?

Yaswanth Varma said...

Looks like the script is trying to install latest Kubernetes version which might have a compatability issue with the version of Ubuntu, i used this an year ago & it worked for K8S version 1.14.

Unknown said...

after inspecting found below error in master and slave by doing "kubectl describe" Error
"runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialize"

Unknown said...

run below from master kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml

Categories

Kubernetes (24) Docker (20) git (13) Jenkins (12) AWS (7) Jenkins CI (5) Vagrant (5) K8s (4) VirtualBox (4) CentOS7 (3) docker registry (3) docker-ee (3) ucp (3) Jenkins Automation (2) Jenkins Master Slave (2) Jenkins Project (2) containers (2) create deployment (2) docker EE (2) docker private registry (2) dockers (2) dtr (2) kubeadm (2) kubectl (2) kubelet (2) openssl (2) Alert Manager CLI (1) AlertManager (1) Apache Maven (1) Best DevOps interview questions (1) CentOS (1) Container as a Service (1) DevOps Interview Questions (1) Docker 19 CE on Ubuntu 19.04 (1) Docker Tutorial (1) Docker UCP (1) Docker installation on Ubunutu (1) Docker interview questions (1) Docker on PowerShell (1) Docker on Windows (1) Docker version (1) Docker-ee installation on CentOS (1) DockerHub (1) Features of DTR (1) Fedora (1) Freestyle Project (1) Git Install on CentOS (1) Git Install on Oracle Linux (1) Git Install on RHEL (1) Git Source based installation (1) Git line ending setup (1) Git migration (1) Grafana on Windows (1) Install DTR (1) Install Docker on Windows Server (1) Install Maven on CentOS (1) Issues (1) Jenkins CI server on AWS instance (1) Jenkins First Job (1) Jenkins Installation on CentOS7 (1) Jenkins Master (1) Jenkins automatic build (1) Jenkins installation on Ubuntu 18.04 (1) Jenkins integration with GitHub server (1) Jenkins on AWS Ubuntu (1) Kubernetes Cluster provisioning (1) Kubernetes interview questions (1) Kuberntes Installation (1) Maven (1) Maven installation on Unix (1) Operations interview Questions (1) Oracle Linux (1) Personal access tokens on GitHub (1) Problem in Docker (1) Prometheus (1) Prometheus CLI (1) RHEL (1) SCM (1) SCM Poll (1) SRE interview questions (1) Troubleshooting (1) Uninstall Git (1) Uninstall Git on CentOS7 (1) Universal Control Plane (1) Vagrantfile (1) amtool (1) aws IAM Role (1) aws policy (1) caas (1) chef installation (1) create organization on UCP (1) create team on UCP (1) docker CE (1) docker UCP console (1) docker command line (1) docker commands (1) docker community edition (1) docker container (1) docker editions (1) docker enterprise edition (1) docker enterprise edition deep dive (1) docker for windows (1) docker hub (1) docker installation (1) docker node (1) docker releases (1) docker secure registry (1) docker service (1) docker swarm init (1) docker swarm join (1) docker trusted registry (1) elasticBeanStalk (1) global configurations (1) helm installation issue (1) mvn (1) namespaces (1) promtool (1) service creation (1) slack (1)