This message was deleted.
# k3sa
adamant-kite-43734
08/15/2023, 12:37 AMThis message was deleted.
c
creamy-pencil-82913
08/15/2023, 2:44 AMno, that should work fine. You might consider running the server agentless so you don’t have to worry about backhauling CNI traffic to your cloud provider… unless you do want it to run core cluster services like dns and such.
creamy-pencil-82913
08/15/2023, 2:45 AMr
red-agent-88261
08/15/2023, 3:06 AMThanks, yes I did read that, I suspect my local proof of concept worked without the wireguard setting because I had the k3 server running in a digital ocean VPS but 2 worker nodes on my local network where they could communicate with each other. I did have the server running agentless already.
Do you know if the official docker rancher/k3s images support wireguard or are there are addition steps required to get that working? I feel like I tried at some point and it didnt work out but didnt spend too much time on it.
red-agent-88261
08/24/2023, 11:41 PMJust following up here in case anybody comes across this thread.
Running a k3s cluster in my companies normal k8s cluster as pod didnt end up working because as far as I've been told there isnt a way to guarantee a pod always gets assigned a true public static IP address that the server needs to setup a wireguard backend, needs to be started with the external IP set correctly as far as I know. The rancher/k3 image does support wireguard but I didnt have a way to know what its public ip address would be all the time if ever.
8 Views