-
Notifications
You must be signed in to change notification settings - Fork 443
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
Switch to AWS CI/CD #1356
Switch to AWS CI/CD #1356
Conversation
--node-type m5.xlarge \ | ||
--nodes 2 \ | ||
--nodes-min 1 \ | ||
--nodes-max 3 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we use managed nodegroup?
Check here: https://github.com/kubeflow/testing/blob/master/images/aws-scripts/create-eks-cluster.sh#L36
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I will use your script to create EKS cluster: https://github.com/kubeflow/testing/blob/master/images/aws-scripts/create-eks-cluster.sh. Since we clone kubeflow/testing
repo to testing NFS, it should be possible.
What do you think @PatrickXYS ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I will use your script to create EKS cluster
Yes we can, reuse common script makes a lot of sense to me.
/test ? |
@PatrickXYS: The following commands are available to trigger jobs:
Use 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. |
Pasted from #1357 The reason that plugin trigger can not trigger prow test:
It's caused by the reason I'm guessing only give write access is not enough, need to investigate Pasted Prow Plugin
|
@PatrickXYS Should we remove access k8s-ci-bot to Katib repo? |
Removing As we discussed in the proposal, Google Prow owns Tide functionality, and AWS Prow owns running tests and report PR status. This should be one of the potential issue with mixed Prow, I'll keep you updated with the progress /cc @andreyvelich |
@PatrickXYS: GitHub didn't allow me to request PR reviews from the following users: andreyvelich. Note that only kubeflow members and repo collaborators can review this PR, and authors cannot review their own PRs. 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. |
I think the problem it won't be enable to fetch org member list to check collaborators. Let's try to see if bot can get
em.. This should be unexpected @andreyvelich is definitely a member. Anything wrong with the upstream prow because of new prow? |
@Jeffwan This is expected, because @andreyvelich can't review his own PR. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: andreyvelich 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 |
@PatrickXYS seems bot does have access to the repo. However, I didn't see it can add label. |
I see. my careless. I thought it's failed to assign. |
/assign @andreyvelich |
/retest |
/test ? |
@PatrickXYS: The following commands are available to trigger jobs:
Use 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. |
@PatrickXYS: The following commands are available to trigger jobs:
Use 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. |
/test kubeflow-katib-presubmit |
@PatrickXYS: The specified target(s) for
Use 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. |
/lgtm |
ccb48bc
to
ce654af
Compare
@johnugeorge @gaocegege I was thinking about temporary solution for the registry. Actually, it is easier to use just another What do you think? |
@andreyvelich: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. I understand the commands that are listed here. |
How will these jobs have access to kubeflow-images-public? |
@jlewi Using |
/lgtm |
Related: #1332.
I will debug the infra in this PR.
I also made few changes to improve CI/CD quality.
/cc @gaocegege @johnugeorge
/cc @Jeffwan @PatrickXYS @jlewi @Bobgy