Simon Vane

**What would you like to be added**: Allow a complete plan to be run at a specific point in another plan. **Why is this needed**: Upgrade processes are often identical...

Document whether tasks run in serial or parallel

2

**What would you like to be added**: Document whether tasks run in serial or parallel **Why is this needed**: It is unclear whether tasks run in serial or parallel and...

Document triggering a plan via the k8s API

1

**What would you like to be added**: Documentation of how to run a specific plan via the k8s API. **Why is this needed**: We are using KUDO in a scenario...

**What would you like to be added**: Provide a way to abandon a plan. 1. Using `kubectl kudo...` 2. By editing the instance/using the k8s API. **Why is this needed**:...

**What would you like to be added**: Provide a way to get the status of tasks in an instance. **Why is this needed**: It would be helpful to be able...

**What would you like to be added**: A means of reducing duplication in our YAML templates, perhaps with similar functionality that helm offers. **Why is this needed**: We would like...

Document the difference between update and upgrade plans

4

**What would you like to be added**: More information to be documented regarding the "well-known" `update` and `upgrade` plans. **Why is this needed**: It is unclear whether there is any...

**What would you like to be added**: It is my understanding that the default strategy for phases and steps is `parallel`. I propose this be changed to serial. **Why is...

**What would you like to be added**: Change the default of `--skip-instance` used in [kubectl-kudo install [flags]](https://kudo.dev/docs/cli/commands.html#install) to be false. **Why is this needed**: It is really easy to forget...

**What would you like to be added**: Documentation of how to upgrade an instance via the k8s API. **Why is this needed**: We are using KUDO in a scenario where...