k3s tls certificate error about k3s HOT 2 CLOSED

K3s servers require a stable, static IP address. You might be able to configure a dummy interface, and use that interface's address as your --node-ip?

For laptops with changing network, you might look at Rancher Desktop, which includes k3s inside a virtual node with isolated networking.

from k3s.

Honestly I don't think this is an answer; this seems like a bug to me. I'm not sure if this will change anything, but I've also pinned the IP of wired NIC on my laptop on my private laptop so it's always the same IP. I understand if the problem were switching between networks ( such as my private and work networks, for example ), AND if the error showed any attempt to connect to a different address ( one that was part of the private network I'm a part of ), but this error shows the connect attempt to a IP that is clearly part of the pod CIDR, which never changes ( the IP of the api-server from inside the cluster? ).

Also, I'm not sure if anyone else is having this issue, but I was able to "solve" the problem by running the k3s-killall.sh script. It seems to kill enough things that seems to erase the problem. Not sure if I lose configuration or stored state information as a result of doing this, but at least it gets me back to being able to collect the logs of the pods again.

Also I feel that this not working runs counter to the mission of k3s being a small, light weight k8s install you can run in edge environments. Of course this is my own opinion and I am no expert in k8s nor fully understanding the entire mission of k8s or k3s.

from k3s.