You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|[HAproxy](http://www.haproxy.org/)| Raspberry Pi |
19
19
|[Docker](https://docs.docker.com/)| Client |
20
20
21
-
`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.
21
+
`Client` refers to the node that will be executing `tofu apply` to create the cluster. The `Raspberry Pi` can be replaced with a VM or a LXC container.
22
22
23
23
Docker is mandatory on the `Client` as this projects builds a custom talos image with system extensions using the [imager](https://github.com/siderolabs/talos/pkgs/container/installer) docker image on the `Client` itself.
24
24
@@ -50,9 +50,9 @@ In the proxmox web portal, go to `Datacenter` > `Storage` > Click on `local` > `
50
50
## Create the cluster
51
51
52
52
```
53
-
terraform init -upgrade
54
-
terraform plan
55
-
terraform apply --auto-approve
53
+
tofu init -upgrade
54
+
tofu plan
55
+
tofu apply --auto-approve
56
56
```
57
57
58
58
## Expose your cluster to the internet (Optional)
@@ -71,4 +71,4 @@ Currently this only happens if you're running this inside on a proxmox node that
71
71
72
72
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.
73
73
74
-
To fix this, either you can give your user access to the interface by adding it to `libvirt`, `libvirt-qemu` and `kvm` groups 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.
74
+
To fix this, either you can give your user access to the interface by adding it to `libvirt`, `libvirt-qemu` and `kvm` groups 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 `tofu apply` finishes.
0 commit comments