K8S lab on Hyperv (WIP)

The idea of this project is to create an easy to deploy Kubernetes environment where different scenarios can be installed to practice Red Team or Pentesting engagements. For now the project only deploy the Kubernetes cluster but different scenarios will be added in the future in the form of Helm charts.

Ansible playbooks used to provision K8S were adapted from torgeirl/kubernetes-playbooks.

Pre-requisites

1. Enable Hyper-V as administrator:

   Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All
   Enable-WindowsOptionalFeature -Online -FeatureName HypervisorPlatform
   Enable-WindowsOptionalFeature -Online -FeatureName VirtualMachinePlatform

2. Install Windows Subsystem for Linux (WSL) as administrator:

   wsl --install -d ubuntu
   wsl --set-version ubuntu 1

3. Add this to /etc/wsl.conf (Inside WSL):

   ...
   [automount]
   enabled = true
   root = /mnt/
   options = "metadata,umask=77,fmask=11"
   mountFsTab = false
   

4. Now restart LxssManager as administrator:

   Restart-Service -Name "LxssManager"

5. Install Vagrant (Inside WSL):

   echo 'export VAGRANT_WSL_ENABLE_WINDOWS_ACCESS="1"' >> ~/.bashrc
   echo 'export VAGRANT_DEFAULT_PROVIDER=hyperv' >> ~/.bashrc
   source ~/.bashrc
   wget -O- https://apt.releases.hashicorp.com/gpg | gpg --dearmor | sudo tee /usr/share/keyrings/hashicorp-archive-keyring.gpg
   echo "deb [signed-by=/usr/share/keyrings/hashicorp-archive-keyring.gpg] https://apt.releases.hashicorp.com $(lsb_release -cs) main" | sudo tee /etc/apt/sources.list.d/hashicorp.list
   sudo apt update && sudo apt install vagrant -y

6. Install this Vagrant plugin (Inside WSL):

   vagrant plugin install vagrant-reload

7. Install Ansible (Inside WSL):

   sudo apt install python3-pip -y
   echo 'PATH=~/.local/bin:$PATH' >> ~/.bashrc
   source ~/.bashrc
   pip3 install ansible

Choosing Kubernetes version

You can tweak what Kubernetes version is gonna be installed by changing the variable kubernetes_version in the file ansible/group_vars/all.yaml.

Deploy

Vagrant is gonna start three Ubuntu machines alongside a NAT switch called T3MSwitch with the IP range 10.10.20.0/24, you may need to tweak this a bit if you have conflicts.

Put the repository directory anywhere outside WSL, for some reason Vagrant hates to be launched in WSL directories. Also, make sure the WSL console is run as administrator:

# If you don't have the switch called 'Default Switch', replace that name from the Vagrantfile and use any other switch with a DHCP server attached
vagrant up

In order to check the cluster status, connect to t3m_athos and login with the credentials vagrant:vagrant. Now execute this:

kubectl get nodes

The command result should be something like:

vagrant@athos:~$ kubectl get nodes
NAME      STATUS   ROLES           AGE     VERSION
aramis    Ready    <none>          2m12s   v1.29.4
athos     Ready    control-plane   146m    v1.29.4
porthos   Ready    <none>          20m     v1.29.4

Clean up

If you want to just get rid of everything execute these commands:

1. Remove lab:

   vagrant destroy -f

2. Uninstall Hyper-V:

   Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All
   Disable-WindowsOptionalFeature -Online -FeatureName HypervisorPlatform
   Disable-WindowsOptionalFeature -Online -FeatureName VirtualMachinePlatform