However, it is an important piece of the puzzle, because my case was a bit different from most cases of an expired OpenShift certificate. I only found out about the root cause later, once I fixed the issue. Then again, I do recall refreshing the certificates at the end of 2020. So when you start a new week, try to log in an see the following output, you know that you forgot about something important: error: x509: certificate has expired or is not yet valid: current time T11:21:55+01:00 is after
And while I have that scripted as well, I need to manually trigger that. So every 60 days, I am refreshing the certificates, which gives me a buffer of 30 days, should something go wrong. Most of that is automated, only the certificate renewal is not. I am running my own OpenShift cluster for a while now, playing with IoT stuff, and using Let’s Encrypt certificates to secure the API server endpoints and the application domain. Here is what happened, or you can directly scroll down for the solution. Fixing and expired OpenShift certificate should be straight forward, but it wasn’t. A not-so-great way to start into a new week, is to figure out that the certificate of your API server expired on the weekend.