Skip to content

refactor(cloud): stop sending the retired tailnet peer-liveness frame - #97

Merged
marvinvr merged 1 commit into
mainfrom
issue-100
Sep 30, 2026
Merged

marvinvr merged 1 commit into
mainfrom
issue-100

Conversation

@marvinvr

Copy link
Copy Markdown
Owner

DockTail Cloud no longer uses local-netmap peer liveness: the tailnet frame is accepted only for compatibility and discarded. This stops reading peers from tailscale status and sending the frame every 30 s.

The same loop also kept this node's MagicDNS name (the Funnel destination) fresh, so that part stays: selfDNSNameLoop re-reads it on the heartbeat cadence (skipped while unmonitored, now bounded by a 5 s timeout). tailscale.TailnetStatus drops the unused peer list.

The proto types are unchanged, so the wire contract is untouched and older clouds are unaffected.

Refs marvinvr/docktail-cloud#100

The cloud no longer reads local-netmap peer liveness: it accepts the
`tailnet` frame only for compatibility and discards it undecoded. Stop
reading peers from `tailscale status` and sending the frame every 30 s.

The same loop also kept this node's MagicDNS name (the Funnel destination)
fresh, so that part stays as selfDNSNameLoop on the heartbeat cadence. The
proto types are unchanged, so the wire contract is untouched.

Refs marvinvr/docktail-cloud#100
@marvinvr
marvinvr merged commit ad8b610 into main Sep 30, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant