Minikube Operations

From NovaOrdis Knowledge Base
Jump to navigation Jump to search




Administration is done with minikube.


minikube instance must be running for "addons" to work.

minikube addons list
minikube addons enable <addon-name>


Start Overview

Start Example

minikube start [-v=10] [--driver=none] [--kubernetes-version "v1.19.1"] 

  minikube v1.12.3 on Darwin 10.14.6
โœจ  Automatically selected the docker driver
๐Ÿ‘  Starting control plane node minikube in cluster minikube
๐Ÿšœ  Pulling base image ...
๐Ÿ’พ  Downloading Kubernetes v1.18.3 preload ...
    > preloaded-images-k8s-v5-v1.18.3-docker-overlay2-amd64.tar.lz4: 510.91 MiB
๐Ÿ”ฅ  Creating docker container (CPUs=2, Memory=8100MB) ...
๐Ÿณ  Preparing Kubernetes v1.18.3 on Docker 19.03.8 ...
๐Ÿ”Ž  Verifying Kubernetes components...
๐ŸŒŸ  Enabled addons: default-storageclass, storage-provisioner
๐Ÿ„  Done! kubectl is now configured to use "minikube"

โ—  /usr/local/bin/kubectl is version 1.16.6-beta.0, which may be incompatible with Kubernetes 1.18.3.
๐Ÿ’ก  You can also use 'minikube kubectl -- get pods' to invoke a matching version

--driver=none option is relevant to accessing host-level directories from pods and exposing them as hostPaths. Also see

Minikube Concepts &124; Drivers

Kubernetes Configuration at Startup
minikube start --extra-config=.... --extra-config=...
minikube start --extra-config=apiserver.enable-admission-plugins=PodSecurityPolicy

Custom Configuration Files

Files placed in ~/.minikube/files (including recursive directories) are transferred into minikube VM. A file placed in ~/.minikube/files/etc/tokens.csv is copied in the VM as /etc/token.csv. That can actually be verified by minikube ssh into the VM after boot.

Start with Admission Controller Enabled

See Enable Pod Security Policies below for an example how to start with a PodSecurityPolicy admission controller.


minikube status

type: Control Plane
host: Running
kubelet: Running
apiserver: Running
kubeconfig: Configured


Stop the local Kubernetes cluster. This command stops the underlying VM or container, but keeps user data intact. The cluster can be started again with the start command.

minikube stop

โœ‹  Stopping node "minikube"  ...
๐Ÿ›‘  Powering off "minikube" via SSH ...
๐Ÿ›‘  1 nodes stopped.


Deletes a local Kubernetes cluster. This command deletes the VM, and removes all associated files.

minikube delete --all --purge

--all deletes all profiles.

--purge deletes delete the '.minikube' folder from the user directory.


minikube dashboard


minikube version

Kubernetes Version

After minikube starts:

kubectl version

Also, nodes report their Kubernetes version:

kubectl get nodes

Also see:

Minikube Configuration

Node Operations

Enable Pod Security Policies
minikube stop
minikube start --extra-config=apiserver.enable-admission-plugins=PodSecurityPolicy --addons=pod-security-policy


CRI-O Support on minikube


If minikube runs in its own VM, host directories can be exposed as hostPath only if they are mounted in the VM. This issue does not exist if minikube does not use a VM and runs in "bare-metal" configuration. See minikube start --driver=none option. Also see

Minikube Concepts | Drivers

Also see:

hostPath on single-node Kubernetes Clusters (minikube, Docker_Desktop_Kubernetes)


Minikube Configuration

minikube logs
minikube start --alsologtostderr --v=2

Obtaining details about kube-apiserver startup arguments:

kubectl -n kube-system describe pod kube-apiserver-minikube

SSH into the minikube VM:

minikube ssh

To get more details about IP and port:

minikube ssh --v=2 --alsologtostderr

Then you can use the IP address ( and the port to connect via native SSH:

ssh docker@ -p 32799 -i ~/.minikube/machines/minikube/id_rsa

For file transfer, a local directory can be mounted into the minikube VM (failed last time I tried it):

minikube mount ~/tmp/minikube:/tmp/temporary

Files can be transferred back and forth via scp:

scp -P 32799 -i ~/.minikube/machines/minikube/id_rsa docker@ .

hostPath Mount Troubleshooting

ssh into the VM:

minikube ssh

Find the container for the pod in question:

docker ps

Describe the container:

docker inspect <container-id>

Look for "Binds".