You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
A datapath upgrade blacks out every VM on a node #774
When an upgrade changes the layout of one eBPF map, the node recreates every map empty, and compute nodes then drop all traffic to their VMs until each VM is recreated.
This hit both staging compute nodes on 2026-10-07 at 02:02 UTC, when one map's key grew.
The next release carries that change and would do the same to every production compute node.
Acceptance criteria
An upgrade that changes one map's layout leaves every other map's contents in place
VMs keep receiving traffic through a datapath upgrade that changes a map's layout
Fixed by #775, #776 and #777, released in v0.5.4. A map layout change now recreates only that map, existing workloads move to the new egress program at startup, and missing attachment rows are rebuilt without recreating workloads. One case the repair misses is tracked in #806.
Activity
fix: Re-attach usid_egress on existing links
refactor: Move attach registration to attachreg
fix: Rebuild attachment datapath rows at startup
privateip commentedon Oct 8, 2026
Fixed by #775, #776 and #777, released in v0.5.4. A map layout change now recreates only that map, existing workloads move to the new egress program at startup, and missing attachment rows are rebuilt without recreating workloads. One case the repair misses is tracked in #806.