Date: 2026-02-06
Record the steps used to move the Kubernetes control plane and node identity to 192.168.1.9 and remove 192.168.1.216.
This was required because earlier control-plane components were pinned to 192.168.1.216, and Gitea cutover depended on a stable Kubernetes ingress target IP.
drg-k8s.Create a working directory:
/home/ax_julian/temp/reip-2026-02-06/Back up:
/etc/kubernetes (tar)/etc/netplan (tar)/etc/default/kubelet: KUBELET_EXTRA_ARGS=--node-ip=192.168.1.9InitConfiguration.localAPIEndpoint.advertiseAddress: 192.168.1.9https://192.168.1.9:6443.192.168.1.9 (regenerate apiserver cert if needed).kubectl get nodes -o wide shows InternalIP 192.168.1.9kubectl cluster-info shows https://192.168.1.9:6443/etc/hosts:
192.168.1.9 drg-k8s.auth.home.lan192.168.1.9/24, and remove the overlay adding 192.168.1.216.ip -4 addr show enp1s0 contains only 192.168.1.9/24 (no 192.168.1.216)kubectl get nodes -o wide InternalIP = 192.168.1.9kubectl cluster-info points at 192.168.1.9If a reverse proxy or SSH forwarder still points at 192.168.1.216, update it to 192.168.1.9:
222 to 192.168.1.9:222.