Minikube Operations
External
Internal
Overview
Administration is done with minikube.
Addons
minikube instance must be running for "addons" to work.
minikube addons list
minikube addons enable <addon-name>
Start
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
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.
Status
minikube status
minikube
type: Control Plane
host: Running
kubelet: Running
apiserver: Running
kubeconfig: Configured
Stop
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.
Delete
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.
Dashboard
minikube dashboard
Version
minikube version
Kubernetes Version
After minikube starts:
kubectl version
Also, nodes report their Kubernetes version:
kubectl get nodes
Also see:
Node Operations
Enable Pod Security Policies
minikube stop
minikube start --extra-config=apiserver.enable-admission-plugins=PodSecurityPolicy --addons=pod-security-policy
CRI-O
Mount
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
Also see:
Configuration
Troubleshooting
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 (127.0.0.1) and the port to connect via native SSH:
ssh docker@127.0.0.1 -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@127.0.0.1:/var/tmp/minikube/kubeadm.yaml .
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".