HFL-Playground-in-k8s is based k8sPlayground .
HFL-Playground-in-k8s sets up a kubernetes cluster on three VirtualBox virtual machines (one master and two workers) running Ubuntu 18.04 LTS using kubeadm.
- k8s specific version = 1.11.0
- docker specific version = docker-ce:17.03
- Switch a pod network, flannel
- Virtual environment with Python3
- Virtualbox 5.2.20
$ git clone https://github.com/WouldULike/HFL-Playground-in-k8s.git
$ cd HFL-Playground-in-k8s
$ pip install virtualenv
$ virtualenv -p python3 k8s_env
// or virtualenv -p python2.7 k8s_env
$ source k8s_env/bin/activateIn the virtual environment, run
$ pip install -r requirements.txt
Install ansible roles.
$ ansible-galaxy install -r requirements.yml -p roles/
Run vagrant up to bring up three virtual machines.
The hostnames and IP addresses of the machines are as follows:
kubemaster — 192.168.99.20
worker1 – 192.168.99.21
worker2 – 192.168.99.22
$ make setup
$ make cluster
As soon as it is done, you can ssh into kubemaster to see the nodes in the cluster by running kubectl get nodes. They may take a while to get ready. You should see something like this:
vagrant@kubemaster:~$ kubectl cluster-info
Kubernetes master is running at https://192.168.99.20:6443
KubeDNS is running at https://192.168.99.20:6443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
vagrant@kubemaster:~$ kubectl get node
NAME STATUS ROLES AGE VERSION
kubemaster Ready master 1m v1.11.0
worker1 Ready <none> 35s v1.11.0
worker2 Ready <none> 34s v1.11.0
$ make clean
This will drain the nodes, make sure that they are empty before shutting them down and reset all kubeadm installed state.
halt the virtual machines
$ vagrant halt
delete the virtual machines
$ vagrant destroy