-
Notifications
You must be signed in to change notification settings - Fork 2.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
Job: migrate ci-kubernetes-e2e-gci-gce-statefulset job to community cluster #31868
Job: migrate ci-kubernetes-e2e-gci-gce-statefulset job to community cluster #31868
Conversation
Hi @soravkumarsharma. 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. |
Can you add the resources on the Lines 27 to 48 in 08e434f
|
@ameukam yeah sure |
@ameukam resources added |
/ok-to-test |
/retest |
/lgtm Please monitor the test for a few days: https://testgrid.k8s.io/google-gce#gci-gce-statefulset. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ameukam, soravkumarsharma 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 |
@soravkumarsharma: 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 ci-kubernetes-e2e-gci-gce-statefulset to community-owned cluster
ref. #31789