search

pipe-cd / pipecd

The One CD for All {applications, platforms, operations}
https://pipecd.dev
Apache License 2.0
1.1k stars 154 forks source link

Make it possible to limit the maximum concurrent deployments that can be performed by a single PipeCD agent #4507

Open nghialv opened 1 year ago

nghialv commented 1 year ago

What would you like to be added:

Why is this needed:

Currently, we are using the PipeCD agent to deploy a large number of Terraform applications. However, the agent starts running all deployments that have been triggered without considering its processing ability. As a result, our PipeCD agent often gets stuck when multiple deployments are triggered simultaneously.

Therefore, I wish we had a way to specify a limit number in the PipeCD agent configuration to prevent it from burning out.

Some other considerations to take into account:

The limit number should be applied to each type of application (e.g., Terraform apps may require more resources to handle than other types of apps). Deployments triggered by plan-preview should also be counted in the limit.

moko-poi commented 1 year ago

👍

github-actions[bot] commented 8 months ago

This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days.