Unable to delete pods and namespaces; stop and start of minikube killed it entirely

[iirekm]

What Happened?

kubectl delete ns devtroncd --grace-period=0 --force - gets stuck, few hours passed an nothing. Never had a such a situation in cloud k8s, kind or k3d, so it must be related to minikube.
It's a fresh installation just installed today.
Version: 1.37.8
OS: Ubuntu 24

Stopping and starting minikube doesn't help either.

Attach the log file

---

Operating System

None

Driver

None

[iirekm]

When I tried to restart again, now minikube start or minikube addons disable also freeze infinitely, headlamp - stopped working, only kubectl works. Thanks minikube for producing these bugs, switching back to k3s!!!

[iirekm]

Output of kubectl get pods -A on this dead minikube:

ambassador       traffic-manager-7ddccc6b8f-vg8k2         0/1     CrashLoopBackOff   16 (84s ago)    17h
devtroncd        app-sync-job-jrj91-74gzk                 0/1     Init:Error         0               104m
devtroncd        postgresql-migrate-casbin-6aizk-4jdg6    0/1     Completed          0               104m
devtroncd        postgresql-migrate-devtron-xzpdw-cdr7w   0/1     Completed          2               104m
kube-system      coredns-66bc5c9577-wnltj                 1/1     Running            5 (7m16s ago)   18h
kube-system      etcd-minikube                            1/1     Running            5 (7m14s ago)   18h
kube-system      kube-apiserver-minikube                  1/1     Running            5 (7m7s ago)    18h
kube-system      kube-controller-manager-minikube         1/1     Running            6 (7m21s ago)   18h
kube-system      kube-proxy-j82kk                         1/1     Running            5 (7m21s ago)   18h
kube-system      kube-scheduler-minikube                  1/1     Running            5 (7m21s ago)   18h
kube-system      metrics-server-85b7d694d7-zjqn5          0/1     CrashLoopBackOff   11 (73s ago)    26m
kube-system      node-shell-minikube-mia651n3-6tw         0/1     Error              0               36m
kube-system      storage-provisioner                      0/1     CrashLoopBackOff   11 (74s ago)    16m
metallb-system   controller-94579fd88-h4mgp               1/1     Running            5 (7m21s ago)   100m
metallb-system   speaker-kt6jm                            1/1     Running            5 (7m21s ago) 

[iirekm]

Logs of failing pods show things like:

panic: unable to load configmap based request-header-client-ca-file: Get "https://192.168.49.2:32443/api/v1/namespaces/kube-system/configmaps/extension-apiserver-authentication": dial tcp 192.168.49.2:32443: connect: connection refused