-
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 kube-batch
jobs to community cluster
#30753
Conversation
Signed-off-by: Lan Liang <[email protected]>
Hi @liangyuanpeng. 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. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: liangyuanpeng The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/ok-to-test |
I know that kube-batch has been archived so not sure if we should migrate this? |
PR needs rebase. 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. |
Ohh, So maybe we should delete the config of kube-batch? Do archived projects still need CI? |
I was told that if a project was archived, we should actually delete this job. Do you want to take that on @liangyuanpeng? |
This PR moves the
kube-batch
jobs from the GCP cluster to the community owned EKS cluster.Ref: #29722
/cc @hex108 @hzxuzhonghu @k82cn