claude-bot
56d55b6228
First step of moving the world-to-pod class onto ingress0 (#576). This changes nothing about where the cluster peers from — it only widens what the UDM will accept. The order matters. Cilium's sessions are outbound to the UDM, and the UDM accepts them through `bgp listen range`. Moving the cluster to ingress0 before the UDM listens on 10.2.47.0/24 would drop every session, and with them every advertised LoadBalancer VIP, so external ingress would go down until the UDM caught up. Listing both segments first removes that window entirely: a listen range only accepts a session, it never opens one, so the 47 ranges sit idle until the cluster actually moves. The prefix-lists and route-maps are untouched. They filter which prefixes the UDM accepts — pod CIDRs and the LB pool — and the cluster advertises the same prefixes either way. Only the next hop changes. Uploaded by hand at UniFi UI -> Settings -> Routing -> BGP, as before. Verify with `vtysh -c "show ip bgp summary"`: the six existing sessions on 10.2.40.x and fd40:: must still be established afterwards, and no new ones appear until the cluster side moves. The 40 ranges come out in a later change, once every session is established on 47. Refs #576