addons.md

title	date	weight	description
Addons	2019-07-31	4	Using addons

minikube has a set of built-in addons that, when enabled, can be used within Kubernetes.

Available addons

• Kubernetes Dashboard
• Heapster: Troubleshooting Guide Note:You will need to login to Grafana as admin/admin in order to access the console
• EFK
• Registry
• Registry Credentials
• Ingress
• Freshpod
• nvidia-driver-installer
• nvidia-gpu-device-plugin
• logviewer
• gvisor
• storage-provisioner-gluster
• helm-tiller
• ingress-dns

Listing available addons

minikube addons list

Example output:

- registry: disabled
- registry-creds: disabled
- freshpod: disabled
- addon-manager: enabled
- dashboard: enabled
- heapster: disabled
- efk: disabled
- ingress: disabled
- default-storageclass: enabled
- storage-provisioner: enabled
- storage-provisioner-gluster: disabled
- nvidia-driver-installer: disabled
- nvidia-gpu-device-plugin: disabled

Enabling an addon

minikube addons enable <name>

or

minikube start --addons <name>

Interacting with an addon

For addons that expose a browser endpoint, use:

minikube addons open <name>

Disabling an addon

minikube addons disable <name>

Custom Addons

If you would like to have minikube properly start/restart custom addons, place the addon(s) .yaml you wish to be launched with minikube in the .minikube/addons directory. Addons in this folder will be moved to the minikube VM and launched each time minikube is started/restarted. Learn [how to develop minikube addons]({{< ref "/docs/contributing/addons.en.md" >}}).