Skip to content
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

Closed
hklai opened this issue Mar 26, 2018 · 22 comments
Closed

Support integration/e2e tests on local machines #4536

hklai opened this issue Mar 26, 2018 · 22 comments

Comments

@hklai
Copy link
Contributor

hklai commented Mar 26, 2018

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.

@hklai hklai changed the title Running integration/e2e tests locally Support integration/e2e tests on local machines Mar 26, 2018
@louiscryan louiscryan assigned louiscryan and unassigned louiscryan Mar 27, 2018
@louiscryan
Copy link
Contributor

/cc @louiscryan

@ozevren
Copy link
Contributor

ozevren commented Mar 27, 2018

/cc @ozevren

@hklai
Copy link
Contributor Author

hklai commented Mar 29, 2018

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:
@kimikowang will try it out on mac, and @JimmyCYJ will try it out on linux.
In the mean time @gargnupur is going to figure out setting up local docker registry.

We will regroup next Monday to share findings.

@kimikowang
Copy link
Member

I am testing the vagrant vm on Mac, but got stuck at the kube-dns brought-up loop in vg-01-repartioton.sh. @JimmyCYJ How is your test on Linux? Does everything work well?

@kimikowang
Copy link
Member

/cc @linsun

@JimmyCYJ
Copy link
Member

JimmyCYJ commented Apr 2, 2018 via email

@JimmyCYJ
Copy link
Member

JimmyCYJ commented Apr 2, 2018

@kimikowang could you try this example?
https://github.com/pires/kubernetes-vagrant-coreos-cluster

It works on my personal desktop (Ubuntu 16.04). I simply run sudo USE_KUBE_UI=true vagrant up.
I get some issues when I run this example in my office workstation, and I am trying to fix.
I am not sure if it works on Mac.

@kimikowang
Copy link
Member

Thanks @JimmyCYJ , let me try to give it a shot.

@JimmyCYJ
Copy link
Member

JimmyCYJ commented Apr 2, 2018

@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.

@kimikowang
Copy link
Member

kimikowang commented Apr 2, 2018

@JimmyCYJ I have no luck in bring up the coreos vm on Mac. It stops at booting stage.

@JimmyCYJ
Copy link
Member

JimmyCYJ commented Apr 2, 2018

@kimikowang There is a trouble shooting section in https://github.com/pires/kubernetes-vagrant-coreos-cluster#troubleshooting. Does it help?

@kimikowang
Copy link
Member

@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.

@JimmyCYJ
Copy link
Member

JimmyCYJ commented Apr 2, 2018

@kimikowang Could you copy and paste parts of the output from your terminal?

@kimikowang
Copy link
Member

Just created an issue under the flux-tech repo: flix-tech/vagrant-kubernetes#12

@JimmyCYJ
Copy link
Member

JimmyCYJ commented Apr 2, 2018

Filed an issue under pires/kubernetes-vagrant-coreos-cluster: pires/kubernetes-vagrant-coreos-cluster#293

@JimmyCYJ
Copy link
Member

JimmyCYJ commented Apr 3, 2018

Filed an issue on missing .kube/config file.
flix-tech/vagrant-kubernetes#13

@ldemailly
Copy link
Member

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)

@gargnupur
Copy link
Contributor

@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
You should be able to run 1 e2e test multiple times..

@ldemailly
Copy link
Member

it wasn't k8s fault but mostly ours

@hklai hklai self-assigned this Jun 4, 2018
@hklai hklai added this to the 1.0 milestone Jun 14, 2018
@stale
Copy link

stale bot commented Jul 15, 2018

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.

@stale stale bot added the stale label Jul 15, 2018
@gargnupur
Copy link
Contributor

This is completed, so closing...

@hklai
Copy link
Contributor Author

hklai commented Jul 16, 2018

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.

@rlenglet rlenglet modified the milestones: 1.4, 1.3, 1.2 Jul 9, 2019
@fpesce fpesce removed this from the 1.2 milestone Jul 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants