feat(bird): put node0 in the pod routing table (#576 step 2)

Pod-sourced traffic is routed from table 47. Once the node IP moves to VLAN 46 (step 3), pods reach node addresses there: the kubernetes ClusterIP (socket LB rewrites it to the apiserver's advertise address), hostNetwork pod IPs, and replies to kubelet probes. Without the attached node0 route in table 47 those flows take the default to the UDM and every in-cluster API client breaks. Taking it from the interface, like the other attached networks, keeps the table in one owner. Refs #576 Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-09-23 13:28:57 +02:00
1 changed files with 1 additions and 1 deletions
@@ -23,7 +23,7 @@ protocol device { scan time 10; }
 # down. The usual advice is not to export these to the kernel because it
 # maintains them itself — true of main, not of a table the kernel never fills.
 protocol direct attached {
-  interface "mgmt0", "ingress0", "pod0";
+  interface "mgmt0", "ingress0", "pod0", "node0";
  ipv4 { table master4; };
  ipv6 { table master6; };
 }