From 82ee70555501760657805c11e12033546adaf9e9 Mon Sep 17 00:00:00 2001 From: theTibi Date: Thu, 3 Sep 2026 21:58:08 +0200 Subject: [PATCH] PMM-15441 Fit the pmm-ha CI install back onto the Kind node The pmm-client StatefulSet added in PMM-14665 (#913) has no override in ci/ci-values.yaml, so CI runs 3 Client pods at 100m CPU each. On the single-node Kind cluster that leaves nothing for the third PMM replica: pmm-ha--2 stays Pending with "Insufficient cpu" and the install hits the 600s timeout. Cap the Clients at 1 and shrink their requests. Also fix clickhouse.keeper.replicas, a key the chart never reads - it is replicasCount - so CI has been running 3 Keepers instead of 1 since January. Together this frees ~450m of requests; the stuck replica needs 200m. Signed-off-by: theTibi --- charts/pmm-ha/ci/ci-values.yaml | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/charts/pmm-ha/ci/ci-values.yaml b/charts/pmm-ha/ci/ci-values.yaml index 7fc10386..3299b573 100644 --- a/charts/pmm-ha/ci/ci-values.yaml +++ b/charts/pmm-ha/ci/ci-values.yaml @@ -12,6 +12,18 @@ pmmResources: memory: "1Gi" cpu: "500m" +# One Client is enough to exercise the StatefulSet. The chart default of 3 does not +# fit next to 3 PMM replicas on the single-node Kind cluster. +pmmClient: + replicas: 1 + resources: + requests: + memory: "128Mi" + cpu: "50m" + limits: + memory: "512Mi" + cpu: "200m" + clickhouse: cluster: shards: 1 @@ -24,7 +36,9 @@ clickhouse: memory: "1Gi" cpu: "500m" keeper: - replicas: 1 + # The chart reads replicasCount (templates/clickhouse-keeper.yaml); a plain + # "replicas" key here is silently ignored, leaving CI on the default of 3. + replicasCount: 1 resources: requests: memory: "512Mi"