Hi all.

As I know, minikube want to use the kubeadm as a install tools rather then the localkube and we can fin d message after we use the localkube as the bootstrapper.

WARNING: The localkube bootstrapper is now deprecated and support for it
will be removed in a future release. Please consider switching to the kubeadm bootstrapper, which
is intended to replace the localkube bootstrapper. To disable this message, run

I have tried to do that for kubernetes v.1.10.0 and I will send a PR #15 to let you see the modification.
Thanks.

tried to do this on my localhost but it fails

Starting local Kubernetes v1.8.0 cluster...
Starting VM...
panic: no-vm not supported

goroutine 1 [running]:

any idea how to fix that?
thanks in advance!

Banged my head trying to get travis wired up for kubernetes to work with our new gradle-kubernetes-plugin. I don't even want to say, or post, what I was doing but the config I had setup was ridiculous and this is infinitely simpler. In either event ... thanks again!

I just want to say thanks for putting this together. I was looking for minikube/travis solution to test MadcoreCLI Your script just made my day :)

To avoid #8 (review) in the future there should also be a few test scenarios besides just deployment creation.

it is unfortunately not just a matter of updating version. it seems that conntrack needs to be provided too:

X Sorry, Kubernetes v1.18.0 requires conntrack to be installed in root's path
The command "sudo minikube start --vm-driver=none --kubernetes-version=v1.18.0" failed and exited with 78 during .

conntrack installation steps here http://conntrack-tools.netfilter.org/manual.html#Installation
(I have not tried yet)

hi,

I want to copy some files into minikube cluster with $HOME/.minikube/files/. However there is an error complaining about no such dir during travis build.

So where could I find this dir. Or alternatively in which way could I copy some files into minikube?

- JSONPATH='{range .items[*]}{@.metadata.name}:{range @.status.conditions[*]}{@.type}={@.status};{end}{end}'; until kubectl -n default get pods -lapp=travis-example -o jsonpath="$JSONPATH" 2>&1 | grep -q "Ready=True"; do sleep 1;echo "waiting for travis-example deployment to be available"; kubectl get pods -n default; done

First and foremost, thanks for the repo example . .
I am having a hard time repurposing this for my needs.
I would like to check that certain pods and operators are able to deploy and delete successfully in my end to end testing .

I was hoping you could go line by line and breakdown the logic of each statement.
Particularly the first two lines I don't understand.

1. '{range .items[*]}{@.metadata.name}:{range @.status.conditions[*]}{@.type}={@.status};{end}{end}'

2. until kubectl -n default get pods -lapp=travis-example -o jsonpath="$JSONPATH" 2>&1 | grep -q "Ready=True";

Questions like these come to mind: the flag -lapp this is a selector right? and what does "$JSONPATH" 2>&1 | grep -q "Ready=True"; mean (2>&1?)?Where did the variable &1 come from?

Thanks
Daniel Moore