Minikube sets up and manages Kubernetes on a single host system, so that you can develop and test clusters on a laptop or a stand-alone server.
Minikube sets up and manage Kubernetes on a single system. This system could be a developer laptop, but it could also be a Linux server. For example, you can run Minikube on a CI system, to provide clusters for your integration tests.
Use Minikube to develop applications that will be deployed on Kubernetes clusters. You can also use it to develop and test cluster configurations.
Minikube uses standard Kubernetes components. This means that all of the tools for Kubernetes should work with Minikube.
How It Works
By default, Minikube uses the virtual machine manager to create a new virtual machine, and installs all of the requirements for Kubernetes in this virtual machine. These requirements include the kubeadm tool, and a container run-time. Current versions of Minikube use Docker as the default container run-time.
If Minikube runs on a Linux operating system, it can set up Kubernetes directly on this system, instead of creating a virtual machine. In this case, you must install a container run-time on the host system yourself.
In either case, Minikube uses kubeadm to set up a Kubernetes cluster on the target machine. First, Minikube installs the minimum set of Kubernetes components to operate a cluster, including the etcd and kubelet services. All of the other components of Kubernetes are then deployed as containers on the cluster, such as the API server and the Scheduler.
Finally, Minikube creates a kubectl context called minikube. This means that the copy of kubectl on the host system automatically connects to the Minikube cluster.
You can use Minikube to set up several different Kubernetes clusters on the same host system.
Manually Setting up Minikube on macOS
If possible, use Homebrew to manage the software on macOS
- Create a ~/.local/bin/ directory
- Add ~/.local/bin/ to your PATH
- Download kubectl for macOS, and copy it to ~/.local/bin/
- Download minikube for macOS, and copy it to ~/.local/bin/
- Install hyperkit (unless you have already installed VirtualBox)
- Install Docker
The Minikube documentation recommends that you use Hyperkit as the virtual machine manager on macOS. If you already use VirtualBox on macOS, you do not need to install Hyperkit, because Minikube supports both types of virtual machine manager.
Install Docker on the macOS host system, so that you can use the command-line tool when you need it. Avoid starting the Docker service, because you will be using Minikube to host your containers.
Creating a Cluster on Minikube
Minikube downloads images and sets up a cluster the first time that you run the minikube start command. Configure Minikube before you start the cluster.
Always specify resource limits before you run the start command:
minikube config set memory 4096 minikube config set cpus 2
You must set a limit of 2 CPUs or higher for the Kubernetes cluster to run.
To pin the Kubernetes version that Minikube uses, add the –kubernetes-version option:
minikube start --kubernetes-version=v1.14.3
Use the –extra-config option to pass other settings to Kubernetes components:
minikube start --extra-config=
This feature uses kubeadm, so you can use the same settings as kubeadm.
By default, clusters use Docker as the container run-time. You can configure a Minikube cluster to use another type of container run-time, such as CRI-O.
Using Minikube for Local Development
To connect to the Docker instance on the Minikube server, use minikube docker-env to set the necessary environment variables:
eval $(minikube docker-env)
Skaffold supports docker-compose files as well as the default skaffold.yaml configuration file.
Use Minikube to launch the Kubernetes Dashboard:
The virtual machine has one IP address. Use NodePorts in Kubernetes to route traffic to specific applications.
Minikube supports attaching local directories on the host to pods in the Kubernetes cluster. This enables you to develop code on the host which immediately runs in containers on the Minikube cluster.
minikube mount $(pwd) /var/www/html
You can also use the container run-time in the Minikube virtual machine to build containers for deployment. Use the minikube docker-env command to output the environment variables that are needed to connect to the container run-time.
eval $(minikube docker-env)
Generating a Configuration File
To share a Minikube configuration between developers, use the features to export and import configurations. The configuration can be in a JSON file, or environment variables.
Use the kubectl command with the –dry-run option and the -o option to create a manifest for a pod in JSON or YAML formats.
Remember to add resource constraints to your pod definitions.
Minikube includes an add-on manager. Several features are provided as addons. For example, the ingress add-on allows access to services that are running on the cluster:
To list the addons:
minikube addons list
To enable an addon:
minikube addons enable ingress
To disable an addon:
minikube addons disable ingress
Editing the Minikube Configuration
Minikube also mounts directories from ~/.minikube/ to the virtual machine. This enables you to customize the virtual machine or the Kubernetes installation.
- Helm - Package manager for Kubernetes
- Skaffold - Deployment tool for Kubernetes
- Ansible Role for Minikube
The Visual Studio Code extension for Kubernetes supports Minikube. For example, it automatically detects the Kubernetes cluster that is provided by Minikube, and includes commands to start and stop Minikube.
- Minikube Intro, by Dan Lorenc, Minikube developer at Google
- Developing Locally with Kubernetes, by Ryan Jarvinen, with slides
- Deep Dive: Minikube, Bálint Pató & Thomas Strömberg - covers the architecture of Minikube, and future directions for the project
- Sharing a Local Container Registry with Minikube, by Hasura
- Run multiple minikube Kubernetes clusters on Ubuntu Linux with KVM, by Alex Ellis
- Minikube on Travis CI, by Kinvolk