I've been seeing errors like `Error running command: -p=TestPersistence start --vm-driver=hyperv --hyperv-virtual-switch=primary-virtual-switch --bootstrapper=kubeadm--wait=false --v=10 --logtostderr --alsologtostderr --v=2 . Output: * minikube v1.2.0 on windows (amd64)` in my hyperV testing which means we need an extra space here.
* Separate start args from args passed to every command. This is so
that we can call `minikube logs` and `minikube status` with the proper
flags (for the bootstrapper)
* Add a NewMinikubeRunner function to make getting a minikube runner
easier.
Theres currently no good way to run the integration tests for the none
driver locally. Now that we've added the e2e target, we can depend on
that. Running the e2e test binary locally requires the testdata folder
to be in a different path, since it is relative to where the code is
being ran. I added a testdata-dir flag to the integration tests so we
can set it appropriately for when we want to run the e2e binary by
itself.
I also made the e2e test binary a PHONY target, so we rebuild it each
time. I had trouble collecting the dependencies on the integration
test packages
Medya Ghazizadeh
AllenZMC
Medya Gh
Sharif Elgamal
Jose Donizetti
tstromberg
Anders F Björklund
Nicholas Goozeff
Matt Rickard
Nick Kubala
dlorenc