#CGGQEHPPW K3s single-node fails to start networking after IP change (“failed to find interface with specified node ip”) Single-node K3s on Ubuntu; host IP changed 192.0.2.10 → 192.0.2.20 (

enp0s31f6

). Set:

--node-ip=192.0.2.20 --tls-san=192.0.2.20

Often see fatal: `error getting node subnet: failed to find interface with specified node ip`; intermittently

kubectl get pods -A

works, other times

ServiceUnavailable/connection refused

. What are the recommended steps to reconcile after an IP change (without wiping datastore)? Any safe CNI cleanup or node/annotation resets to stop the API flapping?