Scooby Husky c2f0f38012 Fix HA failover etcd: advertise via WAN port-forward, not the Netbird mesh IP ...

UniFi's router has no route to 100.108.0.0/16 (the Netbird mesh CIDR) -
it only routes to its own directly-connected LAN. Advertising
talos-cp-01's real Netbird-bound IP (100.108.42.109, confirmed live via
talosctl to be genuinely bound to its wt0 interface - it's real, just
unreachable from outside the mesh) as the etcd client/peer URL would
never actually work for inbound WAN traffic from the VPS/witness.

Corrected to advertise home.kube.huskypup.net on the WAN ports that will
be port-forwarded (12379/12380) to talos-cp-01's real LAN IP
(172.28.101.41) + the NodePort Service - UniFi can route to its own LAN
natively, no extra static routes needed.

2026-08-18 23:25:13 -05:00

..

manifests

Fix HA failover etcd: advertise via WAN port-forward, not the Netbird mesh IP

2026-08-18 23:25:13 -05:00