Automated talos cluster with system extensions
| Dependency | Location |
|---|---|
| Proxmox | Proxmox node |
| xz | Proxmox node |
| jq | Client |
| arp-scan | Client |
| talosctl | Client |
| Terraform | Client |
| HAproxy | Raspberry Pi |
| Docker | Client |
Client refers to the node that will be executing terraform apply to create the cluster. The Raspberry Pi can be replaced with a VM or a LXC container.
Docker is mandatory on the Client as this projects builds a custom talos image with system extensions using the imager docker image on the Client itself.
The main banch will automatically create a VM for a load balancer with 2 CPUs and 2 GiB of memory on your Proxmox node.
You can use the no-lb branch in case you do not want to use an external load-balancer. This branch uses the 1st master node that gets created as the cluster endpoint.
Another option is to use the manual-lb branch in case you wish to create an external lb manually.
The variables needed to configure this script are documented in this doc.
cp terraform.tfvars.example terraform.tfvars
# Edit and save the variables according to your liking
vim terraform.tfvars
terraform init -upgrade
terraform plan
terraform apply --auto-approve
It is possible to expose your cluster to the internet over a small vps even if both your vps and your public ips are dynamic. This is possible by setting up dynamic dns for both your internal network and the vps using something like duckdns and a docker container to regularly monitor the IP addresses on both ends. A connection can be then made using wireguard to traverse the network between these 2 nodes. This way you can hide your public IP while exposing services to the internet.
Project Link: wireguard-k8s-lb
Currently this only happens if you're running this inside on a proxmox node that itself is virtualized inside kvm. This is highly unlikely, but I'll make a note of this for anyone stuck on this.
This project uses arp-scan to scan the local network using arp requests. In case your user does not have proper permissions to scan using the virbr0 interface, then the talos VMs will not be found.
To fix this, either you can update the permissions for that socket interface or you can just use sudo, in case you opt for solution 2, make sure to run the talosctl kubeconfig command generated for you in talos_setup.sh after terraform apply finishes.