-
Notifications
You must be signed in to change notification settings - Fork 7.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support integration/e2e tests on local machines #4536
Comments
/cc @louiscryan |
/cc @ozevren |
Discussed a few options today and @louiscryan suggested starting with https://github.com/flix-tech/vagrant-kubernetes, which is an easier solution to templatise. Current plan: We will regroup next Monday to share findings. |
I am testing the vagrant vm on Mac, but got stuck at the kube-dns brought-up loop in |
/cc @linsun |
I have the same issue, and I tried several fixes but could not solve it.
…On Mon, Apr 2, 2018 at 10:38 AM, Zijun Wang ***@***.***> wrote:
I am testing the vagrant vm on Mac, but got stuck at the kube-dns
brought-up loop in vg-01-repartioton.sh. @JimmyCYJ
<https://github.com/JimmyCYJ> How is your test on Linux? Does everything
work well?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4536 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AbOdjBAFBzRzmVWM-EkiRZfOh1yiKdzWks5tkmIzgaJpZM4S8CEz>
.
|
@kimikowang could you try this example? It works on my personal desktop (Ubuntu 16.04). I simply run sudo USE_KUBE_UI=true vagrant up. |
Thanks @JimmyCYJ , let me try to give it a shot. |
@kimikowang for https://github.com/flix-tech/vagrant-kubernetes, I tried 1.10.0 and 1.9.0 on Ubuntu 16.04, and they failed at different steps. |
@JimmyCYJ I have no luck in bring up the coreos vm on Mac. It stops at booting stage. |
@kimikowang There is a trouble shooting section in https://github.com/pires/kubernetes-vagrant-coreos-cluster#troubleshooting. Does it help? |
@JimmyCYJ Unfortunately no, the problem is at the ssh process to the vm. This seems to be a well-known issue for vagrant, and it seems to be problems with VirtualBox or MacOS. Most of people solved the problem simply by upgrading VB or Mac to latest version. I did that already, but no help. |
@kimikowang Could you copy and paste parts of the output from your terminal? |
Just created an issue under the flux-tech repo: flix-tech/vagrant-kubernetes#12 |
Filed an issue under pires/kubernetes-vagrant-coreos-cluster: pires/kubernetes-vagrant-coreos-cluster#293 |
Filed an issue on missing .kube/config file. |
see #593 (comment) for issues with the previous incantation of the process (though then at least there was a way, albeit undocumented, to run 1 e2e tests multiple times; I'm looking forward to getting back to oct17 state and better) |
@ldemailly : our current test setup looks like should not suffer from issues mentioned in https://github.com/istio/istio/blob/vagrant-kubernetes-istio/vagrant-kubernetes-istio/RunTestOnHost/README.md |
it wasn't k8s fault but mostly ours |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 2 weeks unless it is tagged "help wanted" or other activity occurs. Thank you for your contributions. |
This is completed, so closing... |
To summarize, we have provided two options to run E2E tests on dev machines. The instructions are included in the revamped E2E testing guide at https://github.com/istio/istio/tree/master/tests/e2e. If you encounter any problem, feel free to ping this issue or contact @gargnupur and me directly. |
Context: https://goo.gl/2DPP5o
Figure out and document the steps to run integration/e2e tests using a local cluster (e.g. using Docker on mac/windows, and possibly minikube on linux similar to circleci), instead of having to set up GCP and GKE.
The text was updated successfully, but these errors were encountered: