[BUG] Expired client certificate causes cluster access failure

[Yzi]

Describe the bug
Expired client certificate causes cluster access failure.

To reproduce
Steps to reproduce the behavior:

1. Create a cluster. The default client certificate is valid for one year.
2. Within one year, the k3s version was manually upgraded, but the default client certificate was not updated.
3. One year later, the client certificate expired, causing access to the cluster to fail.

Expected behavior
The client certificate is automatically updated and the cluster can be accessed.

Screenshots
If applicable, add screenshots to help explain your problem.

Environments (please complete the following information):

• OS: [e.g. Darwin Bigsur]
• AutoK3s Version v0.9.2

Additional context
Add any other context about the problem here.

[JacieChao]

@Yzi Thanks for your feedback.

So can I confirm that the K3s certificate can be rotated automatically by the K3s server, after that, the K3s cluster works properly and you can use kubectl on the K3s server properly?
However, AutoK3s is not aware of the certificate change of the K3s cluster. It can't use the existing kubeconfig file(which contains the expired client certificate) to access the K3s cluster.

[Yzi]

The k3s service works normally.
Manually download the certificate automatically rotated by the K3s server, then replace the kubeconfig in the autok3s home directory, restart autok3s and restore access to the k3s service.