I have entered the password of my macbook, and waiting a long time there is no response.
MacBook-Pro:minikube_conf dele$ minikube tunnel
๐ Starting tunnel for service mongo-express-service.
โ The service/ingress dashboard-ingress requires privileged ports to be exposed: [80 443]
๐ sudo permission will be asked for it.
๐ Starting tunnel for service dashboard-ingress.
Password:
my macbook pro version :
macOS Big Sur version 11.5.1
MacBook Pro (Retina, 13-inch, Early 2015)
You need more details to be provided from minikube.
Check out whatโs happening with verbose logging. Hereโs the general troubleshooting guide:
I use
$ minikube tunnel --alsologtostderr --v=2
but still take very long time, and no response log out.
Itโs stuck here:
I1014 15:07:41.527650 9880 loadbalancer_patcher.go:122] Patched mongo-express-service with IP 127.0.0.1
I1014 15:07:41.552551 9880 out.go:177] โ The service/ingress dashboard-ingress requires privileged ports to be exposed: [80 443]
โ The service/ingress dashboard-ingress requires privileged ports to be exposed: [80 443]
I1014 15:07:41.568739 9880 out.go:177] ๐ sudo permission will be asked for it.
๐ sudo permission will be asked for it.
I1014 15:07:41.594756 9880 out.go:177] ๐ Starting tunnel for service dashboard-ingress.
๐ Starting tunnel for service dashboard-ingress.
I log the kubernetes-dashboard pod get below information:
$ kubectl logs kubernetes-dashboard-654cf69797-nxd8f --namespace kubernetes-dashboard
2021/10/14 06:54:55 Starting overwatch
2021/10/14 06:54:55 Using namespace: kubernetes-dashboard
2021/10/14 06:54:55 Using in-cluster config to connect to apiserver
2021/10/14 06:54:55 Using secret token for csrf signing
2021/10/14 06:54:55 Initializing csrf token from kubernetes-dashboard-csrf secret
2021/10/14 06:54:55 Empty token. Generating and storing in a secret kubernetes-dashboard-csrf
2021/10/14 06:54:55 Successful initial request to the apiserver, version: v1.22.2
2021/10/14 06:54:55 Generating JWE encryption key
2021/10/14 06:54:55 New synchronizer has been registered: kubernetes-dashboard-key-holder-kubernetes-dashboard. Starting
2021/10/14 06:54:55 Starting secret synchronizer for kubernetes-dashboard-key-holder in namespace kubernetes-dashboard
2021/10/14 06:54:56 Initializing JWE encryption key from synchronized object
2021/10/14 06:54:56 Creating in-cluster Sidecar client
2021/10/14 06:54:56 Serving insecurely on HTTP port: 9090
2021/10/14 06:54:56 Successful request to sidecar
I1014 11:15:41.262656 1 request.go:668] Waited for 13.3891892s due to client-side throttling, not priority and fairness, request: GET:https://10.96.0.1:443/api/v1/namespaces/kubernetes-dashboard/secrets/kubernetes-dashboard-key-holder
aircrafts-MacBook-Pro:minikube_conf ldl$ kubectl logs kubernetes-dashboard-654cf69797-nxd8f --namespace kubernetes-dashboard
2021/10/14 06:54:55 Starting overwatch
2021/10/14 06:54:55 Using namespace: kubernetes-dashboard
2021/10/14 06:54:55 Using in-cluster config to connect to apiserver
2021/10/14 06:54:55 Using secret token for csrf signing
2021/10/14 06:54:55 Initializing csrf token from kubernetes-dashboard-csrf secret
2021/10/14 06:54:55 Empty token. Generating and storing in a secret kubernetes-dashboard-csrf
2021/10/14 06:54:55 Successful initial request to the apiserver, version: v1.22.2
2021/10/14 06:54:55 Generating JWE encryption key
2021/10/14 06:54:55 New synchronizer has been registered: kubernetes-dashboard-key-holder-kubernetes-dashboard. Starting
2021/10/14 06:54:55 Starting secret synchronizer for kubernetes-dashboard-key-holder in namespace kubernetes-dashboard
2021/10/14 06:54:56 Initializing JWE encryption key from synchronized object
2021/10/14 06:54:56 Creating in-cluster Sidecar client
2021/10/14 06:54:56 Serving insecurely on HTTP port: 9090
2021/10/14 06:54:56 Successful request to sidecar
I1014 11:15:41.262656 1 request.go:668] Waited for 13.3891892s due to client-side throttling, not priority and fairness, request: GET:https://10.96.0.1:443/api/v1/namespaces/kubernetes-dashboard/secrets/kubernetes-dashboard-key-holder
Perhaps this is a bug, Iโm trying to replicate this. Got a few more questions:
What happens if you run minikube with sudo?
Can you provide the output from these commands?
minikube versionminikube statusminikube profile listContinuing from where I left off in thread 17764, you have profile list output that showโs youโre using the docker driver.
Frankly, I have no clue how the docker driver is supposed to drive the networking stack and I canโt replicate it due to not having docker desktop. If I were to ponder a guess, looking at docker network ls would be the first place I start.
Try out the hyperkit driver perhaps. You might need to do a brew install hyperkit. I dropped Docker Desktop with the licensing model being changed, made some notes here for using Minikube instead as well.
$ minikube version
minikube version: v1.23.2
commit: 0a0ad764652082477c00d51d2475284b5d39ceed
$ minikube status
minikube
type: Control Plane
host: Running
kubelet: Running
apiserver: Running
kubeconfig: Configured
$ minikube profile list
|----------|-----------|---------|--------------|------|---------|---------|-------|
| Profile | VM Driver | Runtime | IP | Port | Version | Status | Nodes |
|----------|-----------|---------|--------------|------|---------|---------|-------|
| minikube | docker | docker | 192.168.49.2 | 8443 | v1.22.2 | Running | 1 |
|----------|-----------|---------|--------------|------|---------|---------|-------|
the issue I think should be the bridge0 on my macos is inactive, I am trying to start it up.
Think you might have missed my follow up post after I saw your other thread was possibly related.
I have doubts that bridge0 was created by minikube.