Fix bug when using tailscale config by file #10074
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed Changes
When passing the config of tailscale using the config file, Tailscale was not working correctly in the agent. The reason is that we were setting the variable
cmds.AgentConfig.VPNAuth
which is not used by the agent. A few lines before, k3s is doingcfg := cmds.AgentConfig
and after that, anything set incmds.AgentConfig
will get lost. Therefore, we should set the variablecfg.VPNAuth
instead, which is the one being read by the agent. This PR does exactly thatTypes of Changes
Bugfix
Verification
Deploy k3s+tailscale using the docs and using the
vpn-auth-file
configTesting
Linked Issues
#10064
User-Facing Change
Further Comments