clientupdate: run auto-updates when disconnected from control #12117
Assignees
Labels
Comments
awly
added a commit
that referenced
this issue
May 13, 2024
When the client is disconnected from control for any reason (typically just turned off), we should still attempt to update if auto-updates are enabled. This may help users who turn tailscale on infrequently for accessing resources. Updates #12117
awly
added a commit
that referenced
this issue
May 13, 2024
When the client is disconnected from control for any reason (typically just turned off), we should still attempt to update if auto-updates are enabled. This may help users who turn tailscale on infrequently for accessing resources. Updates #12117 Signed-off-by: Andrew Lytvynov <[email protected]>
awly
added a commit
that referenced
this issue
May 14, 2024
When the client is disconnected from control for any reason (typically just turned off), we should still attempt to update if auto-updates are enabled. This may help users who turn tailscale on infrequently for accessing resources. Updates #12117 Signed-off-by: Andrew Lytvynov <[email protected]>
awly
added a commit
that referenced
this issue
May 14, 2024
When the client is disconnected from control for any reason (typically just turned off), we should still attempt to update if auto-updates are enabled. This may help users who turn tailscale on infrequently for accessing resources. RELNOTE: Apply auto-updates even if the node is down or disconnected from the coordination server. Updates #12117 Signed-off-by: Andrew Lytvynov <[email protected]>
awly
added a commit
that referenced
this issue
May 14, 2024
When the client is disconnected from control for any reason (typically just turned off), we should still attempt to update if auto-updates are enabled. This may help users who turn tailscale on infrequently for accessing resources. RELNOTE: Apply auto-updates even if the node is down or disconnected from the coordination server. Updates #12117 Signed-off-by: Andrew Lytvynov <[email protected]>
awly
added a commit
that referenced
this issue
May 14, 2024
When the client is disconnected from control for any reason (typically just turned off), we should still attempt to update if auto-updates are enabled. This may help users who turn tailscale on infrequently for accessing resources. RELNOTE: Apply auto-updates even if the node is down or disconnected from the coordination server. Updates #12117 Signed-off-by: Andrew Lytvynov <[email protected]>
awly
added a commit
that referenced
this issue
May 14, 2024
When the client is disconnected from control for any reason (typically just turned off), we should still attempt to update if auto-updates are enabled. This may help users who turn tailscale on infrequently for accessing resources. RELNOTE: Apply auto-updates even if the node is down or disconnected from the coordination server. Updates #12117 Signed-off-by: Andrew Lytvynov <[email protected]>
awly
added a commit
that referenced
this issue
May 14, 2024
When the client is disconnected from control for any reason (typically just turned off), we should still attempt to update if auto-updates are enabled. This may help users who turn tailscale on infrequently for accessing resources. RELNOTE: Apply auto-updates even if the node is down or disconnected from the coordination server. Updates #12117 Signed-off-by: Andrew Lytvynov <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What are you trying to do?
When Tailscale is disabled, we should still respect the auto-update setting.
How should we solve this?
No response
What is the impact of not solving this?
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: