Running --merge after re-installing k3s gave a certificate error about k3sup HOT 8 CLOSED

I am having the same issue

from k3sup.

/msg: k3s

from k3sup.

--
This issue appears to be a problem with the upstream k3s project
which k3sup installs and automates.
Please raise an issue on Rancher's GitHub repository and link it
back to this issue for tracking purposes.
https://github.com/rancher/k3s/

from k3sup.

Did you reboot after k3s-uninstall.sh?

What happens if you do not merge, but output to a separate file?

from k3sup.

Given separate discussion on Slack, I'll re-open. This does seem like an edge-case, but happy to look into it further if you can provide more information.

from k3sup.

I'm running into a similar issue. It seems --merge doesn't update any of the cluster info, including the "server" field? k3sup version 0.9.7, k3s version v1.18.15+k3s1 (60f1e80d). I'm mistaken; it doesn't update the client info either.

The workaround is to fetch the client-admin.crt and client-admin.key from /var/log/rancher/k3s/server/tls, base64 encode the contents, and put them into the client-certificate-data and client-key-data fields (respectively) of your kubeconfig context and then do the same for the server-ca.key file (base64 encode it into the kubeconfig cluster's certificate-authority-data field).

from k3sup.

Please raise your own issue and give step by step instructions for reproduction. If you skip and summarise, it'll just delay someone looking into it.

from k3sup.

/lock

from k3sup.