This test typically takes <30s to execute, so 180s should leave plenty
of margin for error.

Signed-off-by: Nmooncake <xcoder@tenxcloud.com>

Update README.md

Remove newline at the start of zsh completion file

Fix typo：miniube-iso -> minikube-iso

Signed-off-by: NBartel Sielski <bsielski@nalys-group.com>

Updated Hyperkit Instructions

The instructions for HyperKit produce the error `install: root: Invalid argument`. @ran-dall Helped me figuire out that root was not being permited foir this command, and sent me the fix for my machine. Figure I'd share it here.

Disable mount tests in Darwin to workaround panic: timeout bug

Globally replace %s format directives with %v for error strings

Add initial documentation for --vm-driver=none

Co-Authored-By: Ntstromberg <tstromberg@google.com>

Update release docs to reflect the state in 2018 (Jenkins!)

Update VM driver instructions to use install(1)

Fix broken TestFunctional/EnvVars test when run under non-bash shell.

v0.30.0: Specifically call out the fixed CVE and omitted #3148

Mention CVE-2018-1002103 on frontpage.

Include ISO URL and reduce stutter in download error message

Let Travis track the latest stable Go 1.x release.

Co-Authored-By: Ntstromberg <tstromberg@google.com>

Co-Authored-By: Ntstromberg <tstromberg@google.com>

Co-Authored-By: Ntstromberg <tstromberg@google.com>

Co-Authored-By: Ntstromberg <tstromberg@google.com>

Co-Authored-By: Ntstromberg <tstromberg@google.com>

Co-Authored-By: Ntstromberg <tstromberg@google.com>

Co-Authored-By: Ntstromberg <tstromberg@google.com>

This commit introduces a new command, `minikube tunnel`, a LoadBalancer emulator functionality, that must be run with root permissions.

This command:

* Establishes networking routes from the host into the VM for all IP ranges used by Kubernetes.
* Enables a cluster controller that allocates IPs to services external `LoadBalancer` IPs.
* Cleans up routes and IPs when stopped (Ctrl+C), when `minikube` stops, and when `minikube tunnel` is ran with the `--cleanup` flag

Make it clear that for none, you must be running standard docker.

These tests reliably cause a "panic: timed out" condition due to
hitherto unknown reasons. See issue #3200 for context.

dlorenc mentioned that this test never worked, so when I re-enabled it
recently for all platforms in af61bf79,
it introduced a persistent test failure for darwin.

I'll leave issue #3200 open until we are able to re-enable this test.