-
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 vsphere-csi-driver
job to community cluster
#31060
Conversation
Signed-off-by: rjsadow <[email protected]>
a3d6583
to
050db08
Compare
/retest |
ping @xing-yang It looks like tests are good now. Thank you |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rjsadow, xing-yang 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 |
@rjsadow: 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. |
@rjsadow jobs started failing after we moved to community cluster. https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/post-vsphere-csi-driver-deploy/1716549353914503168 The pod could not start because it could not mount the volume "cloud-provider-vsphere-e2e-config": secret "cloud-provider-vsphere-e2e-config" not found In the past we moved to default cluster. Ref PR - #29929 |
@divyenpatel I will revert shortly. |
This PR moves vsphere-csi-driver jobs to the community owned cluster.
ref: #30277
/cc @divyenpatel @SandeepPissay @xing-yang @BaluDontu @deepakkinni
/cc @ameukam