What would you like to be added?
It would be useful to have a way to define scenarios such as:
- applying or deleting resources in a specific order
- submitting resources at specific times or intervals
- waiting for conditions before continuing
- repeating the same scenario with different parameters
- coordinating workflow steps with stage-driven state transitions
One possible separation of responsibilities could be:
- Stages handle resource lifecycle progression
- Scenario API handles workflow orchestration such as ordering, timing, and condition-based execution
Why is this needed?
A scenario API could describe how a simulation proceeds at the workflow level, such as ordering, timing, waiting, and repetition.
This would make it easier to define and run experiments where the scenario itself is an important part of the behavior being evaluated, and it would also provide a more reusable and reproducible way to express those workflows.
Related to kubernetes-sigs/kueue#10168
What would you like to be added?
It would be useful to have a way to define scenarios such as:
One possible separation of responsibilities could be:
Why is this needed?
A scenario API could describe how a simulation proceeds at the workflow level, such as ordering, timing, waiting, and repetition.
This would make it easier to define and run experiments where the scenario itself is an important part of the behavior being evaluated, and it would also provide a more reusable and reproducible way to express those workflows.
Related to kubernetes-sigs/kueue#10168