-
Notifications
You must be signed in to change notification settings - Fork 134
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 Kubeflow from k8s-prow #177
Conversation
Needed before this can merge:
Should be done soon (ideally before this merges as well):
This is all I can think of off the top of my head. Lets keep track of all the steps we take so we can leave a guide for transferring service of an org from one Prow instance to another. |
I invited google-oss-robot to the kubeflow org; once the invite is accepted the bot should have write access to Kubeflow repositories
What's the URL to use for these webhooks? Related to: kubernetes/test-infra#14343. |
Paradoxically, the jobs (more specifically |
You can add the jobs in this PR as well or wait to enable Tide until the jobs are added (trigger > jobs > tide). |
/hold |
Related to: kubeflow/testing#475 - Kubeflow issue tracking migration to GoogleCloud Prow |
@jlewi - Apologies for the latency; I have been supporting the Istio 1.4.2 release which just went out today. I need to sync with @cjwagner to disambiguate his last comment.
@cjwagner - if I opt to go for the latter (i.e. wait to enable Tide) this: ( Should these changes (trigger, tide, jobs) be atomic (i.e. one PR)? How can we prevent both duplicate and dropped webhooks in the transition. |
d963231
to
be37da9
Compare
@cjwagner |
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.
/hold
@clarketm is there anything blocking this PR? Are you just waiting on confirmation from me or the Kubeflow build copy (@richardsliu )? My expectation is this PR won't actually cause any downtime so its safe to merge. |
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
581a27d
to
605582e
Compare
2f1e35f
to
2901f4b
Compare
CLAs look good, thanks! ℹ️ Googlers: Go here for more info. |
The following users are mentioned in OWNERS file(s) but are not members of the GoogleCloudPlatform org. Once all users have been added as members of the org, you can trigger verification by writing
|
@googlebot I consent |
I think someone from kubeflow should do this review |
@jlewi can you take a look? |
/assign @jlewi |
/lgtm Thanks @clarketm . My hunch is that some of our more recent changes to our prow jobs may need to be ported over. I think we can do that after this PR is merged though. When this PR is merged; will our tests be running simultaneously on the GCP prow instance as well as the K8s instance? Can we have some transition period during which we verify everything is working correctly on the new GCP instance before turning down the K8s instance? |
@jlewi: changing LGTM is restricted to collaborators 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. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: clarketm, fejta, jlewi 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 |
Replaced by: kubernetes/test-infra#16898 |
Copied
kubeflow
configuration from config and plugins and add tide and jobs.