Go to file
Tanguy Herbron 6f57f55b97 feat(DHCP): Reconfigure IP addesses and ansible inventory
Ansible inventory can now be static with static IPs provisioned by Vangard.
The documentation has also been updated to include how the configuration of the ingress node can be node from any VPS provider.
2023-10-30 16:54:48 +01:00
ansible@920407620d feat(dependency): Add ansible 2023-10-23 14:26:17 +02:00
inventory feat(DHCP): Reconfigure IP addesses and ansible inventory 2023-10-30 16:54:48 +01:00
.gitignore feat(install): Add multiple installation processes 2023-10-23 14:26:55 +02:00
.gitmodules feat(dependency): Add ansible 2023-10-23 14:26:17 +02:00
Makefile feat(DHCP): Reconfigure IP addesses and ansible inventory 2023-10-30 16:54:48 +01:00
README.md feat(DHCP): Reconfigure IP addesses and ansible inventory 2023-10-30 16:54:48 +01:00
Vagrantfile feat(DHCP): Reconfigure IP addesses and ansible inventory 2023-10-30 16:54:48 +01:00

Homelab

Dependencies

  • Vagrant
  • ansible
  • vagrant-scp

Setup

For ingress node connected to the internet, I recommend using a VPS of either choice, acting as the public input to the cluster. To do so, complete the IP in the inventory/outsider.yml file.

This VPS needs to be pre-configured with this script.

Script

  • Detect WSL or Linux
  • Detect default network interface
  • Inject network interface
  • Gather IPs (vagrant ssh-config)
  • Deploy Ansible playbook
  • Download kubeconfig
  • Ping cluster (kubectl get nodes)