-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
setting tailscale's login-server with controlServerURL doesn't work as force-reauth is required with recent version of tailscale #11279
Comments
Are you actually trying to change the control server, or have you had it set to this same URL the whole time? If the tailscale CLI is making you force-reauth even when not actually changing the URL (ie when keeping it set to the same custom value), that seems like a bug in tailscale. Have you opened an issue there? |
i figured out the issue after reading your comment - thank you! k3s runs tailscale commands on the node itself, not some k8s pod or something similar - given i already had a working tailscale client on the node, it would interfere with its config. one thing, i wonder is: what does the integration do on top of "tailscale login" - is it configuring |
k3s/pkg/agent/flannel/setup.go Lines 41 to 45 in 2441e46
And everything around Lines 131 to 151 in 2441e46
|
Environmental Info:
K3s Version:
1.29 and 1.30
Cluster Configuration:
single server
Describe the bug:
setting tailscale's login-server with controlServerURL doesn't work as force-reauth is required with recent version of tailscale
Steps To Reproduce:
curl -sfL https://get.k3s.io | INSTALL_K3S_CHANNEL=v1.29 K3S_KUBECONFIG_MODE="644" INSTALL_K3S_EXEC="server" sh -s - --disable=traefik --tls-san="node.example.com" --vpn-auth="name=tailscale,joinKey=asdfsadfasdfasdfsadfasdfsadfas,controlServerURL=https://example.com,forceReauth=true,extraArgs=--ssh" --node-external-ip=100.64.0.1
Expected behavior:
server should start
Actual behavior:
i get a message in the logs from tailscale that you can't run tailscale up and change login-server without
--force-reauth
.The text was updated successfully, but these errors were encountered: