-
Notifications
You must be signed in to change notification settings - Fork 305
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
[Feature] Update Kubeflow Training Operator 1.9.0 #4066
[Feature] Update Kubeflow Training Operator 1.9.0 #4066
Conversation
Skipping CI for Draft Pull Request. |
✅ Deploy Preview for kubernetes-sigs-kueue canceled.
|
/cc @mimowo |
/ok-to-test |
2b22561
to
56e7931
Compare
/cc @mbobrovskyi for the first pass |
@mimowo: GitHub didn't allow me to request PR reviews from the following users: the, first, pass, for. Note that only kubernetes-sigs 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-sigs/prow repository. |
56e7931
to
f3ec223
Compare
/retest |
f3ec223
to
9fa7049
Compare
/retest |
Should we not merge this until Kubeflow Training Operator has an offical release version? |
Does it fix #1429? |
I think it is ok to merge using rc1, afaik keueue is only using the API from kubeflow and this should not change at this point. Merging this PR would make it easier to work on the follow up which is the support for managedBy in Kueue. While I don't consider it a strict requirement, I would prefer we release Keueue 0.11 in mid March using the full release of Kubeflow. @tenzen-y do you know when the full release is planned? |
/hold Wait for stable release v1.9.x. |
Any particular reason @mbobrovskyi you suggest to wait for 1.9.x, do you mean x>0? Actually, in the past we used to compile against "RC" releases of the frameworks:
Ideally, we use full releases, but I don't think we need to be strict about that. IIUC we only use APIs of these projects, and these would rarely change between candidate and full release. Let me know @tenzen-y @dgrove-oss if you have some opinion here. |
LGTM label has been added. Git tree hash: e7af9f630a9323897a0e6d619d561edddfd299f0
|
/release-note-edit
I think that we can drop the release note since we have a dedicated PR to drop the MXJob supports. |
/hold cancel |
Will update to v1.9.0 as released https://github.com/kubeflow/training-operator/releases/tag/v1.9.0 |
16ac548
to
bdff060
Compare
I'm ok with relying on a bot. A bot will update it to v1.9.0 in the next Monday. |
Oh, you already have addressed that. Awesome! Thank you! |
LGTM label has been added. Git tree hash: 5460cb29c4c7e821d45459557442f43e5104c233
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mszadkow, tenzen-y 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 |
@mszadkow It seems that we need to perform with |
bdff060
to
c002521
Compare
/lgtm |
LGTM label has been added. Git tree hash: a6d65dd2951117ca5bd6ebc06517eb7d6293e616
|
* Update Training Operator pkg to v1.9.0 * Add --server-side for Kubeflow CRDs
What type of PR is this?
/kind feature
What this PR does / why we need it:
Update is required to finally support ManagedBy feature of Kubeflow related jobs.
Which issue(s) this PR fixes:
Relates to #2552
Special notes for your reviewer:
Does this PR introduce a user-facing change?