ERR_CONNECTION_TIMED_OUT after a successful install on minikube (Win11Pro, driver=docker)

[evilguest]

Summary

Hello. I have followed the instruction https://eclipse.dev/che/docs/stable/administration-guide/installing-che-on-minikube/ (Windows 11 Pro, x64).
Everything went fine except for the last command: attempt to open the dashboard shows the ERR_CONNECTION_TIMED_OUT.
Neither does pinging the target address work (192.168.58.2.nip.io).
Where to look for the troubleshooting?

Relevant information

No response

[tolusha]

Hello.
chectl server:logs collects all available logs.
Please inspect them if there are any errors.

[evilguest]

Thanks. Done that, no errors found. I can attach logs here, but I don't see much sense in it.
Looks like something is broken in the network configuration, but I can't figure out what to look for.

For example, kubectl get pods --namespace eclipse-che -o wide yields the following:

NAME                               READY   STATUS      RESTARTS       AGE    IP            NODE       NOMINATED NODE   READINESS GATES
che-8569bd88b-5h6cf                1/1     Running     2 (31m ago)    6d7h   10.244.0.66   minikube   <none>           <none>
che-dashboard-6d544969bc-l7dv6     1/1     Running     1 (91m ago)    6d7h   10.244.0.64   minikube   <none>           <none>
che-gateway-6b64664fc-8zgnn        4/4     Running     10 (29m ago)   6d7h   10.244.0.62   minikube   <none>           <none>
che-operator-69776bf775-wd84p      1/1     Running     2 (31m ago)    6d7h   10.244.0.53   minikube   <none>           <none>
che-tls-job-z4rp7                  0/1     Completed   0              6d7h   <none>        minikube   <none>           <none>
plugin-registry-68b7566f89-cnxhj   1/1     Running     1 (91m ago)    6d7h   10.244.0.59   minikube   <none>           <none>

How do I check the ports/forwardings?

[evilguest]

Additional info (maybe this helps): minikube service list yields

|-------------------------|-----------------------------------------|--------------|-----|
|        NAMESPACE        |                  NAME                   | TARGET PORT  | URL |
|-------------------------|-----------------------------------------|--------------|-----|
| cert-manager            | cert-manager                            | No node port |     |
| cert-manager            | cert-manager-webhook                    | No node port |     |
| default                 | kubernetes                              | No node port |     |
| devworkspace-controller | devworkspace-controller-manager-service | No node port |     |
| devworkspace-controller | devworkspace-controller-metrics         | No node port |     |
| devworkspace-controller | devworkspace-webhookserver              | No node port |     |
| dex                     | dex                                     | No node port |     |
| eclipse-che             | che-dashboard                           | No node port |     |
| eclipse-che             | che-gateway                             | No node port |     |
| eclipse-che             | che-host                                | No node port |     |
| eclipse-che             | che-operator-service                    | No node port |     |
| eclipse-che             | plugin-registry                         | No node port |     |
| ingress-nginx           | ingress-nginx-controller                | http/80      |     |
|                         |                                         | https/443    |     |
| ingress-nginx           | ingress-nginx-controller-admission      | No node port |     |
| kube-system             | kube-dns                                | No node port |     |
| kubernetes-dashboard    | dashboard-metrics-scraper               | No node port |     |
| kubernetes-dashboard    | kubernetes-dashboard                    | No node port |     |
|-------------------------|-----------------------------------------|--------------|-----|

[evilguest]

Looks like the root of all evil is driver=docker in minikube.
Relevant information can be found here: https://stackoverflow.com/questions/71714919/unable-to-access-my-minikube-cluster-from-the-browser-because-you-are-using-a

Reverting the deployment to the hyper-v driver (as recommended in the response marked as answer) did the trick for me:

Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-Tools-All -All

[evilguest]

Can be closed now.