[Discussion] Future of recurring run (a.k.a job or scheduled workflow)
See original GitHub issueThere were a lot of discussion in https://github.com/kubeflow/pipelines/issues/3789 that I think worth grouping in a new issue.
Our conclusion for Job (a.k.a recurring run/scheduled workflow) is: We may work on a refactoring that swaps out underlying
ScheduledWorkflow
implementation with kubernetesCronJob
, that will be best for long term maintenance. We don’t want to maintain our ownScheduledWorkflowController
that is a feature subset ofCronJob
. UsingCronJob
as implementation details allow first party integration like UI management, metadata for pipeline runs for CronJob, while keeping maintenance cost low for the controller.We don’t have an ETA for the refactoring right now, because
Job
is not our priority, we’ll triage based on future user requirements.
Originally posted in https://github.com/kubeflow/pipelines/issues/3789#issuecomment-662296647
Issue Analytics
- State:
- Created 3 years ago
- Comments:39 (38 by maintainers)
@Bobgy @NikeNano Also, would this be a good time to pick one single name, used across the entire code base? It’s funny that even this issue and design doc reference the same feature with 3 different names. I think “Recurring Run” is the more idiomatic term, but really any name is fine as long as we agree on one.
That’s awesome💯💯 Can you share comment permission to me?