Minikube

2 minute read page test

Follow these instructions to prepare minikube for Istio installation with sufficient resources to run Istio and some basic applications.

Prerequisites

Administrative privileges are required to run minikube.
To enable the Secret Discovery Service (SDS) for your mesh, you must add extra configurations to your Kubernetes deployment. Refer to the api-server reference docs for the most up-to-date flags.

Installation steps

Install the latest version of minikube and a minikube hypervisor driver.
If you’re not using the default driver, set your minikube hypervisor driver.
For example, if you installed the KVM hypervisor, set the driver within the minikube configuration using the following command:
```
$ minikube config set driver kvm2
```
Start minikube with 16384 MB of memory and 4 CPUs. This example uses Kubernetes version 1.17.5. You can change the version to any Kubernetes version supported by Istio by altering the --kubernetes-version value:
```
$ minikube start --memory=16384 --cpus=4 --kubernetes-version=v1.17.5
```
Depending on the hypervisor you use and the platform on which the hypervisor is run, minimum memory requirements vary. 16384 MB is sufficient to run Istio and bookinfo.
If you don’t have enough RAM allocated to the minikube virtual machine, the following errors could occur:
- image pull failures
- healthcheck timeout failures
- kubectl failures on the host
- general network instability of the virtual machine and the host
- complete lock-up of the virtual machine
- host NMI watchdog reboots
One effective way to monitor memory usage in minikube is to ssh into the minikube virtual machine and from that prompt run the top command:
```
$ minikube ssh
```
```
$ top
GiB Mem : 12.4/15.7
```
This shows 12.4GiB used of an available 15.7 GiB RAM within the virtual machine. This data was generated with the VMWare Fusion hypervisor on a Macbook Pro 13” with 16GiB RAM running Istio 1.2 with bookinfo installed.
(Optional, recommended) If you want minikube to provide a load balancer for use by Istio, you can use the minikube tunnel feature. Run this command in a different terminal, because the minikube tunnel feature will block your terminal to output diagnostic information about the network:
```
$ minikube tunnel
```
Sometimes minikube does not clean up the tunnel network properly. To force a proper cleanup:
```
$ minikube tunnel --cleanup
```

Was this information useful?

Do you have any suggestions for improvement?

Thanks for your feedback!