Actively working on a Microsoft Teams tab.
Has this been abandoned? I would love to see first-class support for this in the Subscriptions feature.
In fact, all that needs to be done is to enable multiple full installations of tentacles on a server, in different directories. These can then be added to cluster resources.
I second this - we also have time periods where workload is high for our apps, and users would like to have a rollout freeze to prevent possible issues.
In this case, I would just give Child Steps a Start Trigger field, just like their parent's settings. The setting would allow child steps of a single top-level step to run in parallel with each other. Then, depending on the setting of the next top-level step, its children could also run in parallel with the first group of children.
For example for the following structure:
If Step 1.2 has a start trigger which lets it run in parallel, it would run at the same time as Step 1.1.
If Step 2 is set to wait for Step 1 to finish, it will wait until all the children are done.
If Step 2 is set to run in parallel with Step 1, then I would expect Step 2.1 to be able to run at the same time as Steps 1.1 and 1.2.
Likewise, if Step 2.2 is set to run in parallel, it could run at the same time as Steps 1.1 and 1.2.
If Step 2.2 is set to wait for the previous step to finish, it would wait for Step 2.1 to finish before running.
To summarize, the Child Step Trigger setting would affect whether or not children of the same step can run together, while the trigger setting on the parent would determine if the children could start in parallel of another top-level step.
Note that also, without this feature, it is not possible to take advantage of rolling deployments and parallel steps at the same time.