This message was deleted.
# k3s
a
This message was deleted.
c
I would recommend using the tailscale integration in order to ensure that the CNI is set up properly
🎯 1
It is covered in the docs
👍 1
b
I did use the intergration.
The nodes all show up on the tailscale admin console and 3 of the 4 nodes say that they advertise routes while the last one does not.
I am using the default flannel CNI and the command I used to install k3s is
curl -sfL <https://get.k3s.io> | sh -s - --disable servicelb --disable traefik --tls-san "REDACTED" --node-external-ip "REDACTED" --vpn-auth="name=tailscale,joinKey=REDACTED"
I have also added the auto approve rules for subnet routes in the tailscale access controls.
@creamy-pencil-82913?
Nevermind, fixed it by using the tailscale ip as the server ip on the agents instead of the public ip.