Separate workflow scheduling and execution #6

Open
opened 2024-07-03 10:46:49 +02:00 by pb · 0 comments
Owner

In the near future we want to extract the workflow execution task from oc-scheduler.
There would need to be another service which will execute the argo workflow. This will prevent any error in the execution part to impact the scheduler and vice versa.

This new service would need to :

  • be created on the fly : one container for each new WF execution
    OR
  • be able to create new namespace to differentiate execution within the k8s cluster
    OR/AND
  • be able to create new process in the case it is not running on in a k8s cluster.
In the near future we want to extract the workflow execution task from oc-scheduler. There would need to be another service which will execute the argo workflow. This will prevent any error in the execution part to impact the scheduler and vice versa. This new service would need to : - be created on the fly : one container for each new WF execution OR - be able to create new namespace to differentiate execution within the k8s cluster OR/AND - be able to create new process in the case it is not running on in a k8s cluster.
pb added the
Priority/Medium
label 2024-07-03 10:46:49 +02:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: core/oc-schedulerd#6
No description provided.