enough-carpet-2091510/08/2022, 5:58 PM
I tried doing
Error from server: error dialing backend: x509: certificate is valid for 127.0.0.1, 45.x.x.x, 2a02:c206:xxxx:xxxx::1, not 38.x.x.x
(from https://github.com/k3s-io/k3s/wiki/K3s-Cert-Rotation) which seems to have rotated certs, but I'm still getting the same error.
k3s certificate rotate
creamy-pencil-8291310/08/2022, 7:47 PM
enough-carpet-2091510/08/2022, 8:00 PM
creamy-pencil-8291310/08/2022, 8:51 PM
enough-carpet-2091510/08/2022, 8:53 PM
creamy-pencil-8291310/08/2022, 8:53 PM
enough-carpet-2091510/08/2022, 8:55 PM
curl -sfL <https://get.k3s.io> | K3S_TOKEN=SECRET sh -s - server --cluster-init
creamy-pencil-8291310/08/2022, 8:56 PM
enough-carpet-2091510/08/2022, 8:57 PM
creamy-pencil-8291310/08/2022, 8:57 PM
for the node with the pod on it, and what is the output when you run
kubectl get node <NODENAME> -o yaml
on that node?
openssl x509 -noout -text -in /var/lib/rancher/k3s/agent/serving-kubelet.crt
address in the error the old or current address of the node with the pod, or the server?
enough-carpet-2091510/08/2022, 9:00 PM