Closed matthewmichihara closed 4 years ago
I'm also seeing this on the latest HEAD
version of minikube, obtained from https://storage.googleapis.com/minikube-builds/master/minikube-darwin-amd64:
$ ./minikube version
minikube version: v1.13.1
commit: 0fc0c82337876cff676790bec417f7d674e63eb9
For some reason, the gcp-auth addon is trying to inject credentials into the storage-provisioner pod on cluster restart even though I've explicitly excluded the kube-system namespace entirely. I'll look into why that's happening.
After the following line is printed, minikube hangs for roughly 30s:
📌 If you don't want your credentials mounted into a specific pod, add a label with the
gcp-auth-skip-secretkey to your pod configuration.
Optional: Full output of
minikube logs
command: