k.rennerandClaude Opus 4.7
b4b0df8a29
The previous /24 installed `10.2.30.0/24 dev net1` as a connected route in HA's pod namespace. k8s-edge's reported InternalIP is `10.2.30.137` (its v30iot address), so music-assistant's hostNetwork pod registers that as the service endpoint. HA's ClusterIP → DNAT path then resolved to `10.2.30.137:8095`, the kernel re-routed via `dev net1` (10.2.30.0/24 match), and the packet went out net1 with src=10.244.x.x — wrong subnet for v30iot, kernel returned "Host unreachable". HA→music-assistant broke. /32 keeps net1 attached for mDNS multicast reception (group membership, not unicast routing) without claiming the IoT VLAN subnet inside the pod's route table. Unicast cluster-internal traffic stays on eth0 where Cilium can manage it; Shelly HTTP unicast to 10.2.30.x continues via eth0 → cluster routing → gateway (the path that's worked the entire time, and what the user pointed out is correct). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>