Menu

Restarting Tailscale silently isolated a k3s node: fixing a flannel VXLAN bug upstream
📰

Restarting Tailscale silently isolated a k3s node: fixing a flannel VXLAN bug upstream

DEV Community: kubernetes·Ryan·about 3 hours ago
#dwK3Wk74
#devtokubernetes#devto#dev#flannel#node
Long article (1388 words) — no AI summary yet.
Reading 0:00
15s threshold

This is an English version of my original Japanese article on Zenn , translated with the help of AI.

TL;DR

On k3s with the flannel VXLAN backend running over a VPN interface (Tailscale here), restarting or upgrading tailscaled left one node unable to reach Pods on any other node. The node stayed Ready and nothing alerted.

flannel recreated flannel.1 , but the kernel had already dropped the routes, ARP and FDB entries that went through it, and flannel only rewrites those when a remote lease changes .

The fix replays the known remote leases after the device is recreated: flannel-io/flannel#2618 , released in v0.28.11 (a pre-release as of 2026-11-20).

Until your k3s ships it, restart k3s / k3s-agent after a VPN restart and alert on the number of flannel.1 routes.

Issue: vxlan: routes/ARP/FDB not restored after the external interface is recreated (#2617)

Who this affects: anyone running the flannel VXLAN backend (including k3s's embedded flannel) with --iface ( flannel-iface in k3s) set to a VPN interface…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.