Remove Matter Server node pin and expose API through MetalLB

apps/matter-server/README.md

@@ -6,10 +6,17 @@ alongside Home Assistant. Its chart version in `bootstrap/matter-server.yaml`
 is the canonical release selection; the upstream chart selects its images.
 
 Home Assistant connects to `ws://matter-server.default.svc.cluster.local/ws`.
-The server uses host networking on `intel-xeon`, with `enp1s0` as its primary
-LAN interface. The MikroTik OTBR remains the Thread border router; Matter
-Server does not create another Thread network. The WebSocket/dashboard port
-is LAN-only and has no public ingress.
+The server uses host networking for LAN multicast and IPv6 connectivity to
+Matter devices. It has no node selector, fixed listen address, or fixed
+interface name; Kubernetes can reschedule it with the same CephFS claim.
+MetalLB allocates a LAN address for the WebSocket/dashboard Service. That
+address covers API access, not Matter discovery or device traffic: the
+node running the controller still needs working LAN IPv6 routes to the OTBR.
+The cluster's Cilium pod network is IPv4-only, so a LoadBalancer Service
+alone cannot replace host networking. The MikroTik OTBR remains the Thread
+border router; Matter Server does not create another Thread network.
+There is no public ingress. A single controller restarts during rescheduling;
+this is recovery with preserved state, not uninterrupted active-active service.
 
 The MikroTik-managed `app-otbr` container requires these startup sysctls in
 its own network namespace: `net.ipv6.conf.all.forwarding=1`,

apps/matter-server/values.yaml

@@ -2,11 +2,8 @@ fullnameOverride: matter-server
 bluetoothCommissioning:
   enabled: true
   mode: proxy
-networkInterface: enp1s0
-listenAddresses:
-  - 192.168.0.3
-nodeSelector:
-  kubernetes.io/hostname: intel-xeon
+service:
+  type: LoadBalancer
 persistence:
   storageClassName: rook-cephfs-ec
 resources: