From 188cb8ad8108505af07486656e3bbbdd8dd27615 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Hugo=20Ar=C3=A8s?= Date: Mon, 18 Mar 2024 18:53:02 -0400 Subject: [PATCH] Increase appstudio pods quota (#993) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Even though this quota is named for--deployments implying that it only affects deployments, this is not the case and it does block the build. This quota cap the number of pods in a namespace, including the completed ones. Not only the build tasks can no longer start, it looks like this does block some kind of pod cleanup because as soon as I increased the quota, not only builds started but overall number of pods started to go down after slightly increasing over 300. PipelineRun usually have about 10 tasks or more so 300 pods, not counting deployments, allows maximum 30 PipelineRun which is too low. The pod counts includes the completed ones so since PipelineRun are not deleted right after completion, we need to increase that quota to not end up in this situation all the time. The final number will need fine tuning but for now increase it to 600 as I experimented on tenant's namespace where the issue was seen and 600 allowed to not get the issue again until now. KONFLUX-2454 Signed-off-by: Hugo Arès --- deploy/templates/nstemplatetiers/appstudio/cluster.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy/templates/nstemplatetiers/appstudio/cluster.yaml b/deploy/templates/nstemplatetiers/appstudio/cluster.yaml index 6bac357e3..743227082 100644 --- a/deploy/templates/nstemplatetiers/appstudio/cluster.yaml +++ b/deploy/templates/nstemplatetiers/appstudio/cluster.yaml @@ -132,7 +132,7 @@ parameters: - name: DEPLOYMENT_QUOTA value: "30" - name: POD_QUOTA - value: "300" + value: "600" - name: ROUTE_QUOTA value: "30" - name: SERVICE_QUOTA