Skip to content

fix(xfrminion): use netlink directly for bridge fdb, not the bridge binary - #34

Open
m4ci3k2 wants to merge 1 commit into
dialohq:masterfrom
m4ci3k2:fix/xfrminion-bridge-fdb-netlink
Open

fix(xfrminion): use netlink directly for bridge fdb, not the bridge binary#34
m4ci3k2 wants to merge 1 commit into
dialohq:masterfrom
m4ci3k2:fix/xfrminion-bridge-fdb-netlink

Conversation

@m4ci3k2

@m4ci3k2 m4ci3k2 commented Sep 1, 2026

Copy link
Copy Markdown

Mirrors cmd/vxlandlord's fix for the same issue: the ko-built image has
no bridge/iproute2 binary, so shelling out to it always fails with
"exec: "bridge": executable file not found in $PATH". Replaces both
the add and delete paths (and the delete path's extra bridge fdb show | grep | xargs bridge fdb del cleanup pipeline) with equivalent
netlink calls (NeighAppend/NeighDel/NeighList).

Verified: go build/vet/gofmt clean, and confirmed at runtime in a live
cluster - the xfrm-pod's restctl calls to add/delete FDB entries now
succeed instead of failing on a missing binary.

…inary

Mirrors cmd/vxlandlord's fix for the same issue: the ko-built image has
no bridge/iproute2 binary, so shelling out to it always fails with
"exec: \"bridge\": executable file not found in $PATH". Replaces both
the add and delete paths (and the delete path's extra `bridge fdb show
| grep | xargs bridge fdb del` cleanup pipeline) with equivalent
netlink calls (NeighAppend/NeighDel/NeighList).

Verified: go build/vet/gofmt clean, and confirmed at runtime in a live
cluster - the xfrm-pod's restctl calls to add/delete FDB entries now
succeed instead of failing on a missing binary.
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.

2 participants