Skip to content

Commit

Permalink
Add known issue
Browse files Browse the repository at this point in the history
Naman1997 committed May 24, 2024
1 parent 3246c67 commit 19c83e0
Showing 1 changed file with 10 additions and 1 deletion.
11 changes: 10 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
@@ -73,4 +73,13 @@ curl -k https://192.168.0.101
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](https://github.com/Naman1997/wireguard-k8s-lb)
Project Link: [wireguard-k8s-lb](https://github.com/Naman1997/wireguard-k8s-lb)


## Known Issue with Proxmox in KVM

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` generated for you in `talos_setup.sh` after `terraform apply` finishes.

0 comments on commit 19c83e0

Please sign in to comment.