Skip to content
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

feat(backend): Allow recurring runs to always use the latest pipeline version #11560

Merged
merged 2 commits into from
Jan 31, 2025

Conversation

mprahl
Copy link
Contributor

@mprahl mprahl commented Jan 27, 2025

Description of your changes:

This makes the pipeline_version_id optional and makes the
Scheduled Workflow controller levarege the REST API to launch the run
rather than rely on compiled Argo Workflows stored in the
ScheduledWorkflow object.

The previous behavior is preserved if the user is using the v1 API or
specifies a pipeline version ID or pipeline spec manifest.

Resolves:
#11542

Checklist:

Copy link

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@mprahl
Copy link
Contributor Author

mprahl commented Jan 27, 2025

/cc @HumairAK

@google-oss-prow google-oss-prow bot requested a review from HumairAK January 27, 2025 20:53
@mprahl mprahl force-pushed the swf-no-pv branch 3 times, most recently from 5b49142 to 7ccdbad Compare January 27, 2025 21:53
@google-oss-prow google-oss-prow bot added size/XL and removed size/L labels Jan 27, 2025
@mprahl mprahl force-pushed the swf-no-pv branch 17 times, most recently from 0beb1b2 to 1f5dbf8 Compare January 29, 2025 20:54
@mprahl mprahl force-pushed the swf-no-pv branch 4 times, most recently from 53d82c0 to f6ac254 Compare January 30, 2025 14:57
@mprahl mprahl changed the title WIP: Allow recurring runs to always use the latest pipeline version feat(backend): Allow recurring runs to always use the latest pipeline version Jan 30, 2025
@mprahl mprahl marked this pull request as ready for review January 30, 2025 15:38
@google-oss-prow google-oss-prow bot requested a review from rimolive January 30, 2025 15:38
This makes the pipeline_version_id optional and makes the
Scheduled Workflow controller levarege the REST API to launch the run
rather than rely on compiled Argo Workflows stored in the
ScheduledWorkflow object.

The previous behavior is preserved if the user is using the v1 API or
specifies a pipeline version ID or pipeline spec manifest.

Resolves:
kubeflow#11542

Signed-off-by: mprahl <[email protected]>
@HumairAK
Copy link
Collaborator

/lgtm
/approve

tested/verified

Awesome !

Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: HumairAK

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@google-oss-prow google-oss-prow bot merged commit 9c5b72c into kubeflow:master Jan 31, 2025
33 checks passed
@HumairAK
Copy link
Collaborator

@mprahl can we get an issue for front end support on this?

@mprahl
Copy link
Contributor Author

mprahl commented Jan 31, 2025

@mprahl can we get an issue for front end support on this?

Filed at #11581.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants