Because we don’t have to mess up our local machine with dev configuration! We already know that all the cool devs are using Docker for the local development environment. And there is Kuberenetes for the coolest group. But if we want to try out the application in a local Kubernetes node before deploying it to the production, things might become a bit complicated. And we have an hassle free solution for it! Let’s see how we can do that. The only prerequisite is — Docker. Let’s assume we already have Docker installed and running. minikube (alternative) We can use minikube to run and test an application (image) in local Kubernetes. But it is super slow (my Macbook Pro starts radiating heat after a while). So, we are not going to use it. kind (Kubernetes) We are going to use — kind. It is runs local Kubernetes cluster in Docker container. Thus, it requires very little time to up and stop the Kubernetes node. We can follow the Quick Start section of their official docs to install kind. After we are done installing kind, we can create our Kubernetes cluster with the following command — kind create cluster --name local It may take a while to download the Docker image for the first time and we will see the following output when the cluster is created. Now, we have a running Kubernetes cluster for local development. Thankfully, it automatically switches to the newly created kubectl context :) Next stop, Helm! Helm Helm is a package manager for Kubernetes. We will use it to deploy our Kubernetes Dashboard with just a single line of command. Follow the installation guide in the official documentation to install Helm. If you are running OSX like me and using Homebrew then just run the following command in terminal brew install helm Kubernetes Dashboard Add Chart Repo Helm uses a chart file to deploy any application. These chart files hold the configuration for that application that defines the controller, service, secret, and other resources for the application. A reposito