minikube: Expired certs not being renewed

What Happened?

This was supposed fixed in issue 10122 but I dont think this is fixed. Or at least not as I would expect it to be fixed. Ive linked the issue from my repo here. You can check my https://github.com/Kimi450/ubuntu_server/issues/4#issuecomment-1483833790on that issue which describes why I think its broken (and how to replicate it). Unless im doing something wrong, I think this issue still persists.

Basically, if you use --cert-expiration tag, that only affects

/var/lib/minikube/certs/proxy-client.crt
/var/lib/minikube/certs/apiserver.crt

# these are on my mounted ones, minikube start --mount --mount-string "/home/kimi450:/minikube-host" --cert-expiration="120s"
/minikube-host/.minikube/profiles/minikube/proxy-client.crt
/minikube-host/.minikube/profiles/minikube/client.crt
/minikube-host/.minikube/profiles/minikube/apiserver.crt

and the problematic (not renewed) ones are

/var/lib/minikube/certs/etcd/healthcheck-client.crt
/var/lib/minikube/certs/etcd/server.crt
/var/lib/minikube/certs/etcd/peer.crt
/var/lib/minikube/certs/apiserver-etcd-client.crt
/var/lib/minikube/certs/apiserver-kubelet-client.crt
/var/lib/minikube/certs/front-proxy-client.crt

Without these being renewed, the minikube instance cannot be accessed (unless you change the system time to a date in the past)

minikube version

minikube version: v1.29.0
commit: ddac20b4b34a9c8c857fc602203b6ba2679794d3

Reproduce by doing the following

  • install minikube (no special setting required)

  • change system time

    timedatectl
    timedatectl set-ntp no
    
    # some time in the future, more than a year 
    timedatectl set-time 2025-08-10
    
  • restart minikube (optional)

    minikube stop
    minikube start
    

Attach the log file

I do not have this at the moment, but I can provide later if absolutely necessary

Operating System

Ubuntu

Driver

Docker

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 17 (8 by maintainers)

Most upvoted comments

this bug has been bugging me for years ! good job @Kimi450 and @spowelljr on helping to investigate it