Basically, everyone who starts working with Kubernetes cluster, begins with kubectl (and helm, probably). This is the way, like Mandalorian would say; that’s the official tool, the Kubernetes official documentation relies on it, and there are numerous examples how to use it. Using kubectl, you kill pods, you scale deployments, you take a glance at logs, and so on. High chances are, that like almost everybody else, you quickly find it to be a bit tedious and notice it involves a lot of long commands with switches like
--namespace. So you create cryptic aliases or install some helper commands like
In this entry-level article, I present a simple way to build, expose and test your dockerized application in local development environment with Minikube, essentially Kubernetes on your computer. Sometimes the developers struggle with handling the experimental images, because for every image change, they push it to the registry and then pull it on the test K8s cluster. Below, we will use only local environment — this is going to work even if you don’t have a network connection.
We will gather necessary tools, install Minikube and build and test our own sample application.
1. You can easily run simple Kubernetes environment with Minikube on your own laptop without creating VMs. …