Count of pipelineruns with status in Running and Queued >= containerCapStr, may trigger deadlock

[chilianyi]

trafficstars

What is version of KubeSphere DevOps has the issue?

v3.3.1

How did you install the Kubernetes? Or what is the Kubernetes distribution?

kubekey

What happened?

The default containerCapStr in jenkins casc config is 2.

If two or more pipelines are running, two or more base pod are created, more than containerCapStr: 2 Then each pipelinerun will stop and wait to create new pod to execute next stage, but no one is able to create new pod.

If Count of pipelineruns with status in Running and Queued < containerCapStr, will not trigger deadlock

Should add this check in controller.

Relevant log output

No response

Additional information

No response