Minikube edits the kubernetes configuration file referenced by the
To preserve the original configuration either make a backup of the
relevant file, or change
KUBECONFIG to a different path specific to
the intended deployment.
Deployment and teardown
For developing with Minikube, start a local cluster by running the
bazel run //dev/minikube:start
And tear it down again via:
bazel run //dev/minikube:delete
Managing system resources
The following three environment variables are used by the
target to allocate the resources used by the deployed Minikube:
||the number of CPUs Minikube will use.|
||the amount of RAM Minikube will be allowed to use.|
||the disk size Minikube will be allowed to use.|
VM_CPUS=6 VM_MEMORY=$((1024 * 24)) VM_DISK_SIZE=180g bazel run //dev/minikube:start
Specifying a different Kubernetes version
K8S_VERSION environment variable to override the default version.
At the moment, only the VirtualBox and KVM2 drivers are working correctly. Set the
environment variable to override the default. E.g.
Extra minikube options
It is possible to set extra minikube options (e.g. to set a docker registry
mirror) via the environment variable
MINIKUBE_EXTRA_OPTIONS. For example:
export MINIKUBE_EXTRA_OPTIONS="--registry-mirror http://registry.mirror.example:5000/"