-
Notifications
You must be signed in to change notification settings - Fork 40.3k
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
[e2e node] gcloud is included even local #31597
Conversation
GCE e2e build/test passed for commit 53c1c0c. |
@resouer why do we need |
Because we changed to use gci by default for local development, and we need gcloud to get newest gci image. However, the logic should be in remote run, not local run. I'll fix it. |
@Random-Liu sounds good. Let's close this PR. |
@resouer Thanks a lot! Good catch~ :) |
Automatic merge from submit-queue Node E2E: Move the image and host related logic to be remote run specific. This PR addresses #31597, and better fixes #31588. With this PR: 1) All remote logic is moved into remote mode. 2) All gci related logic is only called when `HOSTS` and `IMAGES` are not specified. 3) Run node e2e against other node e2e images will work again - `make test-e2e-node REMOET=true IMAGES=e2e-node-containervm-v20160321-image`. 4) List images will work again - `make test-e2e-node REMOTE=true LIST_IMAGES=true`. Mark 1.4, because #31588 is marked as 1.4. And this makes the node e2e work as is described in the [doc ](https://github.com/kubernetes/kubernetes/blob/master/docs/devel/e2e-node-tests.md#run-tests-using-different-images). @yujuhong @vishh /cc @kubernetes/sig-node
Even when running e2e node test locally, we still need
gcloud
on PATH, though it does not need to start any instances in cloud.So I suggest add a node in doc at least, otherwise, people may feel confused (so I did).
cc @yujuhong
This change is