Hi All, I am getting the problem when trying to fix expired cert of k3s cluster using system-upgrade . I set the back date and follow the instruction given here (https://docs.k3s.io/upgrades/automated) but pods (system-upgrade-controller-8677c8fb4-4mg6h) is in pending state

What certificate is that for? That SN/SKID/AKID format subject is not something that k3s generates. I suspect it’s something else in your environment?

@creamy-pencil-82913 The cert is the internal k3s cert

we don’t generate certs with subjects like that. are you sure?

It looks to me the k3s cert. Do you know how to fix this problem ?

it is not a k3s cert. That is the cert of some client that is trying to authenticate to k3s. I don’t know what it is, because it’s not in a format that we generate, so it must be coming from something else.

@creamy-pencil-82913 Thanks for the reply. I managed to fix the problem after updating the master node to latest version using

curl -sfL <https://get.k3s.io> | sh -

and then I followed the upgrade steps mentioned here https://docs.k3s.io/upgrades/automated

🤷

@creamy-pencil-82913 After ssl cert fix and updating the k3s cluster the

kubectl

commands is responding very slow and sometime it is getting timeout and getting

Unable to connect to the server: net/http: TLS handshake timeout

error message. Due to this the application exposed via ingress stop working and getting 502 error. So do you know how to fix this problem.??