From the command line, you can run kubectl commands. You can now start deploying Kubernetes resources to your cluster. Once that turns green, you have Kubernetes up and running! Click Cancel to exit the settings. In the bottom left of the screen you can see the little Kubernetes symbol has appeared, but it's orange to indicating it's still starting up. Click Install to continue.ĭocker Desktop pulls all the required images in the background, and starts setting up your cluster. Navigate to the Kubernetes tab, and check Enable Kubernetes:Ĭlick Apply & Restart, and you'll get a popup advising you that you need an internet connection. Check Enable Kubernetes in Docker DesktopĪfter you've followed the instructions in my previous post to install WSL 2 and Docker Desktop, open up the settings screen (by clicking the cog in the top right).Install WSL 2 and Docker Desktop for Windows.You only need to do two things to get Kubernetes running in Docker Desktop: There are many other ways to run Kubernetes locally, such as using kind or minikube, but if you're already using Docker Desktop, then this is probably the easiest approach.

This is very convenient, as you'll see shortly! Kubernetes can run on top of Docker ( currently), and Docker Desktop for Windows (or Mac) includes support for running a Kubernetes cluster for you, without you having to manually configure the cluster yourself.

Enabling Kubernetes on Docker Desktop for Windows The downside to that is it means running your own Kubernetes cluster locally… Luckily, Docker Desktop can take care of that for you!įor an introduction to Kubernetes, or for advice on deploying ASP.NET Core applications to Kubernetes, see my 12 part series. That said, if you're deploying to production on Kubernetes then there's considerable value to being able to run and test your code in a similar environment locally. NET space, then Project Tye is another great option which should give a simpler onboarding than Kubernetes. Even if you find you start needing to orchestrate containers locally, I'd recommend Docker Compose as a simpler alternative to Kubernetes. You don't need Kubernetes to benefit from that. In my experience, the biggest wins from Docker come from the isolation it gives you from your host system. Kubernetes has become the defacto container orchestrator for production workloads, but that doesn't mean you necessarily need it. Your first question before going down this route should be 'do I need Kubernetes?'. In this post I show how to enable Kubernetes support, and how to deploy the Kubernetes Dashboard to give your local Kubernetes cluster a friendly GUI. In my previous post, I showed how you can install Docker Desktop for Windows using WSL 2.

Run docker on kubernetes secret