-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
migrate pull-ingress-gce-e2e to use community clusters #31846
Conversation
Hi @sawsa307. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions 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. |
/hold Wait until kubernetes/ingress-gce#2458 gets merged |
/ok-to-test |
Yes I added a hold on this PR, with the reference to the PR needed in the |
/retest |
Just approved kubernetes/ingress-gce#2458, we should be able to merge this as soon as the PR in ingress-gce merges. |
/unhold |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ameukam, sawsa307 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Thanks @ameukam! After this gets merged I'll re-trigger our job and see it there is any issue. |
@sawsa307: Updated the
In response to this:
Instructions 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. |
This PR moves pull-ingress-gce-e2e jobs to the community owned cluster gke cluster.
ref: #30277
parent: #31681 and #31736