Replies: 1 comment
-
Not sure why this was converted to a question. This is a feature request. I can open a PR for it if y'all agree with my approach: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Is your feature request related to a problem? Please describe.
I have an existing set of nodes that are already connected to Tailscale. In order to use the k3s Tailscale integration I am forced to pass through a JoinKey and have k3s manage connecting to Tailscale.
Describe the solution you'd like
I need k3s to manage advertising routes and such, but leave connecting to Tailscale up to me. This would mean making the joinKey optional, and if it's not present skipping the
tailscale up
command, perhaps even verifying that Tailscale is not connected.Describe alternatives you've considered
I've tried to manually use the tailscale network with
--flannel-iface=tailscale0
but I'm not sure how to correctly advertise routes for pods, since I assume those can be pretty dynamic?Additional context
My primary use case is that we are working towards a much more complex authentication scheme that would not be compatible with pre-authenticated keys, as well as I just don't want to be exposing authkeys in my config.
Beta Was this translation helpful? Give feedback.
All reactions