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.
PR descriptionm
Background
Networks that use tailscale have their interface specified in
tailscale<vpn-id>
liketailscale0
ortailscale1
etc.By default, the hostname that is picked up by the interactive session is of the local lan interface (or the public ip interface). Technically this doesn't matter, as the ssh session is actually alive, and the cli only points to the wrong address. So even if the interactive session via the cli fails, one could always ssh into the session using the
ssh
and replacing the target IP stored in the clearml task, by the actual tailscale IP address. But for this one needs to do some digging and look into the clearml task to find out which host the session was launched itChanges proposed
This PR makes the change of broadcasting the tailscale IP into the task configuration if the
--tailscale
option is given.Implementation
--tailscale
as an argument in the CLI