Minkube being repeatedly started and stopped every 3 seconds

[asampal]

Environment:

Extension version:
1.6.1

VSCode version:
Version: 1.51.0-insider (user setup)
Commit: 89c002ab02f87102d91efc83c191ef1174756c6a
Date: 2020-10-15T23:17:08.035Z
Electron: 9.3.2
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Windows_NT x64 10.0.19041

OS:
OS Name Microsoft Windows 10 Pro
Version 10.0.19041 Build 19041

Docker Desktop:

Description:
Minikube continuously starts and restarts about every 3 seconds. This happens at any time, i.e. even before the k8s cluster is started from the status bar, through the time that the cluster is running and continues after the cluster is stopped. Note that the docker-desktop cluster is also running all the while.

Repro step:
Install the above versions of VSCode, the extension, and Docker Desktop and monitor the running processes.

[kschaab]

I think this is a call to minikube status, it shouldn't be starting anything, are you seeing it start something?

[asampal]

No, there's nothing visual - where should I look?

[asampal]

If you look at the command line, it looks like it's doing both minikube profile list and minikube status.

[kschaab]

Yes, we are looking at ways to address this. For the time being you can turn off minikube status bar if you don't require it. That will prevent this behavior.

[asampal]

Just noticed now that when this open/close happens lots of log files are created in the temp directory. There were about 140 000. Including a zip containing what was emitted over just one minute. Note that some of these (not all I think - only saw some messages about the docker demon not being found in a brief look) might have been generated because Docker Desktop isn't running all the time - it was running when this issue was reported, though. IMO not having Docker Desktop shouldn't create spurious logs.

minikube.exe.logs.zip

[sivakku]

@asampal - We are working on releasing a hotfix soon that would address this issue. Thank you for your patience.

[redborian]

The hotfix has been released. Feel free to try the latest release and provide feedback @asampal

[asampal]

Thanks, for the heads-up. I use the Insiders version so I got the fix immediately. Seems fine now.