Hello, I was trying to upgrade my cluster with the following command:

sudo curl -sfL <https://get.k3s.io> | INSTALL_K3S_VERSION=v1.24.11+k3s1 INSTALL_K3S_EXEC="--write-kubeconfig-mode "0644" --kubelet-arg=config=/etc/rancher/k3s/kubelet-config.yaml --disable=traefik --cluster-cidr=172.16.0.0/16 --flannel-backend=none --disable-network-policy --datastore-endpoint=etcd --default-local-storage-path=/mnt/storage" sh -

However I didn't have the kubelet config file in place

/etc/rancher/k3s/kubelet-config.yaml

at that moment making the k3s not starting properly

...
[INFO]  systemd: Creating service file /etc/systemd/system/k3s.service
[INFO]  systemd: Enabling k3s unit
Created symlink /etc/systemd/system/multi-user.target.wants/k3s.service → /etc/systemd/system/k3s.service.
[INFO]  systemd: Starting k3s
Job for k3s.service failed because the control process exited with error code.
See "systemctl status k3s.service" and "journalctl -xeu k3s.service" for details.

Once the file was in place, k3s started but now I see two nodes:

kubectl get no
NAME             STATUS     ROLES                       AGE    VERSION
old-desired      Ready      control-plane,etcd,master   323d   v1.23.6+k3s1
new-undesired    NotReady   control-plane,etcd,master   118s   v1.24.11+k3s1

Is there a way to remove that

undesired

node without affecting the

desired

node?

delete it?