Conversation
|
/LGTM |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: andraxylia The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
|
Please wait. @frankbu FYI. |
|
The shell e2e is the only one that works on minikube, so before it's removed the go version should be fixed to work in minikube too. |
|
@frankbu Have you tried the --use-local-cluster when running the tests ? |
|
I don't think this is any different: Line 84 in c2208fe https://github.com/istio/istio/blob/master/tests/e2e/util/kubeUtils.go#L165 I think the golang framework changes loadbalander to nodePort such that it does not create the ingress. |
|
@sebastienvas please make sure it runs first, maybe ask someone with minikube (I don't have on installed yet, sorry). The flag name |
|
@kyessenov I am asking @ZackButcher to test, I am just stating that the shell framework does not have anything different to make it work on minikube. |
|
@sebastienvas I had not tried |
|
/lgtm cancel //PR changed after LGTM, removing LGTM. @andraxylia @sebastienvas |
|
@frankbu I added some documentation. Please review. |
| In order to talk to istio ingress, we use the ingress IP by default. If your | ||
| cluster is on the same local network and cannot provide external IP, use the `--use-local-cluster` flag. | ||
| In that case, the framework will not create a LoadBalancer and talk directly to the Pod running istio-ingress. | ||
|
|
There was a problem hiding this comment.
This looks good but I would suggest "... cannot provide external IP (for example, minikube), use ...".
I also think you should remove the this sentence from the top of the README: "We recommend GKE cluster although miniKube works for some people too". It works fine for minikube.
|
@sebastienvas: The following test failed, say
DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
/retest |
* Tagging minor version when creating a new tag * Removed unused date * Added a check for the version * Fixes matcher Former-commit-id: de23c84208cc9fe71a1fdd63b1cdebf4d3d22ae1
* Remove shell e2e test * Documents -use-local-cluster * Fix documentation Former-commit-id: 34f530e
* Tagging minor version when creating a new tag * Removed unused date * Added a check for the version * Fixes matcher Former-commit-id: 8f4e88c18acda2daf158df1a49599c0bebbf1e78
* Remove shell e2e test * Documents -use-local-cluster * Fix documentation Former-commit-id: 34f530e
* Remove shell e2e test * Documents -use-local-cluster * Fix documentation Former-commit-id: 34f530e
* Add tsan and asan * remove @
Automatic merge from submit-queue. Bring back accidentally deleted build options in istio#736 **What this PR does / why we need it**: istio#736 accidentally remove `-c opt` from release build and a couple of compile options, bring them back. cc @costinm @ldemailly **Special notes for your reviewer**: **Release note**: ```release-note None ```
Removing deprecated e2e test framework in favor of the golang framework
Fixes #645
Fixes #185