<p>Most tutorials I've seen for developing with Kubernetes locally use Minikube. In the latest Edge release of Docker for Windows, you can also enable Kubernetes. I'm trying to understand the differences between the two and which I should use.</p>

<ol>
<li>Minikube lets you choose the version of Kubernetes you want, can Docker for Windows do that? I don't see a way to configure it.</li>
<li>Minikube has CLI commands to enable the dashboard, heapster, ingress and other addons. I'm not sure why because my undertstanding is that these are simply executing <code>kubectl apply -f http://...</code>. </li>
<li>With Minikube I can do a <code>minikube ip</code> to get the cluster IP address for ingress, how can I do this with Docker for Windows?</li>
<li>Is there anything else different that I should care about.</li>
</ol>

<p>I feel like you largely understand the space, and mostly have answers to your questions already.  You might find <a href="https://docs.docker.com/docker-for-mac/docker-toolbox/" rel="noreferrer">Docker for Mac vs. Docker Toolbox</a> an informative read, even if it's about the Mac equivalent rather than Windows and about Docker packaged as a VM rather than Kubernetes specifically.</p>

<ol>
<li><p>In fact you are stuck with the specific version of Kubernetes the Docker Edge desktop distribution publishes.</p></li>
<li><p>is answered in the question.</p></li>
<li><p>I believe NodePort-type Services are published on your host's IP address; there isn't an intermediate VM address like there is with Docker Toolbox.</p></li>
<li><p>Docker Toolbox and minikube always use a full-blown virtual machine with an off-the-shelf hypervisor.  The Docker desktop application might use a lighter-weight virtualization engine if one is available.</p></li>
<li><p>Kubernetes can involve some significant background work.  If you're using Kubernetes-in-Docker it's hard to "turn off" Kubernetes and still have Docker available; but if you have a separate minikube VM you can just stop it.</p></li>
</ol>
