Starting minikube failed after loooong period of disuse

[RanchoHam]

What Happened?

Haven't run minikube on this particular machine (Win11 Pro on HP-Z06 hardware with Docker Desktop installed and running) for well over a year. The minikube start barfed with the following ...
`💾 Downloading Kubernetes v1.30.0 preload ...
> preloaded-images-k8s-v18-v1...: 342.90 MiB / 342.90 MiB 100.00% 32.34 M
> gcr.io/k8s-minikube/kicbase...: 481.58 MiB / 481.58 MiB 100.00% 30.62 M
🔥 Creating docker container (CPUs=2, Memory=16300MB) ...
🐳 Preparing Kubernetes v1.30.0 on Docker 26.1.1 ...
❗ kubeadm certificates have expired. Generating new ones...

❌ Exiting due to GUEST_CERT: Failed to setup certs: renew expired kubeadm certs: kubeadm certs renew: /bin/bash -c "sudo env PATH="/var/lib/minikube/binaries/v1.30.0:$PATH" kubeadm certs renew all --config /var/tmp/minikube/kubeadm.yaml": Process exited with status 1
stdout:

stderr:
this version of kubeadm only supports deploying clusters with the control plane version >= 1.29.0. Current version: v1.27.4
To see the stack trace of this error execute with --v=5 or higher`

logs.txt

Attach the log file

Haven't run minikube on this particular machine (Win11 Pro on HP-Z06 hardware with Docker Desktop installed and running) for well over a year. The minikube start barfed with the following ...
`💾 Downloading Kubernetes v1.30.0 preload ...
> preloaded-images-k8s-v18-v1...: 342.90 MiB / 342.90 MiB 100.00% 32.34 M
> gcr.io/k8s-minikube/kicbase...: 481.58 MiB / 481.58 MiB 100.00% 30.62 M
🔥 Creating docker container (CPUs=2, Memory=16300MB) ...
🐳 Preparing Kubernetes v1.30.0 on Docker 26.1.1 ...
❗ kubeadm certificates have expired. Generating new ones...

❌ Exiting due to GUEST_CERT: Failed to setup certs: renew expired kubeadm certs: kubeadm certs renew: /bin/bash -c "sudo env PATH="/var/lib/minikube/binaries/v1.30.0:$PATH" kubeadm certs renew all --config /var/tmp/minikube/kubeadm.yaml": Process exited with status 1
stdout:

stderr:
this version of kubeadm only supports deploying clusters with the control plane version >= 1.29.0. Current version: v1.27.4
To see the stack trace of this error execute with --v=5 or higher`

logs.txt

Operating System

Windows

Driver

Docker

[RanchoHam]

Sorry about the double paste, I mis-understood what the form wanted.

[Test-Script]

It looks like the current cluster was using Kubernetes v1.27 and kubeadm certificates that had already expired. Kubeadm versions that come with minikube (v1.30) can't renew certificates for clusters that are older than v1.29.

The workaround that will be worked:

1. minikube delete --all --purge
2. minikube start

[nirs]

I0310 09:57:32.049693 27992 out.go:177] 😄 minikube v1.33.1 on Microsoft Windows 11 Pro For Workstations 10.0.26200.7922 Build 26200.7922

@RanchoHam why are you using minikube 1.33.1 when the latest release is 1.38.1?

[RanchoHam]

@nirs Because that was what was currently installed when I tried to revive the old project.

[nirs]

@RanchoHam sure, is this reproducible with latest minikube version? If not we can close this issue.

[RanchoHam]

Go ahead and close it, as the minikube delete --all-purge & minkube start sequence mentioned by @Test-Script worked for me.