Hi everyone, I am using K3S on a Fedora CoreOS installation. Below you can find the details of this virtual machine:

k3s --version
k3s version v1.33.2+k3s1

cat /etc/fedora-release
Fedora release 41 (Forty One)

On this machine, I need to install K3S using an ignition file on a specific subnet with an open internet connection. Then, I switch the public IP of the machine to a new one inside a DMZ using nmcli. Below you can find an example of the commands that my customer has used:

sudo nmcli connection mod 'Wired connection 1' \
  ipv4.method manual \
  ipv4.addresses 199.178.20/24 \
  ipv4.gateway 199.178.20.254 \           
  ipv4.dns 199.178.20.254 \
  +ipv4.dns 8.8.8.8 \
  connection.autoconnect yes

sudo nmcli connection up 'Wired connection 1'
sudo systemctl restart NetworkManager.service

# Updating K3S_URL with the new IP: <https://199.178.20:6443>
sudo systemctl stop k3s.service
sudo nano /etc/systemd/system/k3s-agent.service.env
sudo systemctl start k3s.service

After these changes, I experienced some connectivity issues because the node of the K3S cluster maintains the IP address of the old machine. I've done several tests on this issue, and I've found out that with an older version of K3S that is used inside other machines, I didn’t have this kind of problem. This specific version is this one:

k3s --version
k3s version v1.31.6+k3s1

Is this a known issue? Do you see any errors in my procedure? For additional information, I would also like to underline that my K3S installations are using a state DB, so they are not an etcd cluster, hence I cannot use HA solutions at the moment.