Impact on Talos Kubernetes Cluster Stability When DHCP IP Addresses Change Due to Lease Expiration

[H-haonan]

I'm running a 3-master Kubernetes cluster on Talos Linux where all node IP addresses are dynamically assigned via DHCP. I understand that Talos supports DHCP for IP allocation, but I'm concerned about what happens when the DHCP leases expire and the IP addresses change (e.g., due to lease timeout or DHCP server behavior).
Specifically:

What is the expected cluster state after IP addresses change? Will the cluster remain operational, or could it lead to issues like etcd peer disconnection, API server unavailability, or pod scheduling failures?
Is the cluster still stable in this scenario? For example, does Talos handle IP changes gracefully, or does it require manual intervention to recover?
If the IPs change, can I continue managing the cluster (e.g., via talosctl or kubectl) using the newly assigned IP addresses? Would I need to update any configurations, such as the kubeconfig or machine configs, to point to the new IPs?

From my understanding, Kubernetes components like etcd and the control plane rely on stable endpoints. If IPs change without static DHCP reservations, it might disrupt the cluster. I'd appreciate any insights, best practices, or documentation references on using DHCP in production Talos clusters.
Thanks for your help!

[rothgar]

If the IP addresses for a multi-node etcd cluster change the cluster will fail to verify members and will break. Other components such as the kubernetes endpoint can use a virtual IP address (VIP), load balancer, etc. The Talos API will still be available on the new IP address via talosctl.

It is recommended you assign the IP address statically via the machine config or a DHCP reservation.