Ability to Skip In-Progress Batches in RolloutRun

[Wenfeng-GAO]

Dear KusionStack Team,

I am an avid user of the KusionStack rollout project, and I would like to suggest a new feature that I believe would greatly enhance its functionality and flexibility.

Feature Request

I propose the addition of a feature that would allow users to skip in-progress batches during a RolloutRun. This feature would enable operators to bypass certain batches that are deemed unnecessary or if a critical issue has been identified that warrants them to halt and move onto the next batch without completing the current one.

Current Limitations

Currently, users are required to let each batch in a RolloutRun to either fully complete or fail before moving on to subsequent batches. However, there might be scenarios where the need to skip an in-progress batch arises, and the current system does not accommodate this level of control.

[zoumo]

I need to rethink the skip operation and need to answer the following questions

1. Should we allow skipping of ongoing grayscale releases
2. Should we allow skipping of ongoing batch releases
3. How should we safely skip them to properly recycle or revert changes made during the release process, such as the release generating new workloads, services, routes, etc.?