From ff9d96057ac3386764adf9b4b5bec2a2f453afce Mon Sep 17 00:00:00 2001 From: Lily Shen Date: Mon, 27 Apr 2026 15:34:12 -0700 Subject: [PATCH] chore(deploy-dev): bump helm --burst-limit 200 --qps 100 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Helm upgrade has been failing with `client rate limiter Wait returned an error: context deadline exceeded` on every revision since rev 67. Initial diagnosis blamed the 5m timeout (#244 bumped to 10m) and then RBAC (deploy SA needed admin in commonly-dev — applied out-of-band). Both helped marginally, but the underlying cause is helm's own internal client QPS limiter throttling itself during --wait status polling. Helm 3.14 supports --burst-limit and --qps. Defaults are 100/50 (since 3.10) but a chart with 30+ resources times out at the default during --wait readiness polling. 200/100 doubles the budget — keeps helm from self-throttling without raising load on the API server (which is happy to serve at much higher rates). Reference: helm/helm#9805 Co-Authored-By: Claude Opus 4.7 (1M context) --- .github/workflows/deploy-dev.yml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/.github/workflows/deploy-dev.yml b/.github/workflows/deploy-dev.yml index 1b4adc82d..1142ec336 100644 --- a/.github/workflows/deploy-dev.yml +++ b/.github/workflows/deploy-dev.yml @@ -142,7 +142,9 @@ jobs: --set agents.clawdbot.image.tag="$TAG" \ --set agents.commonlyBot.image.tag="$TAG" \ --wait \ - --timeout 10m + --timeout 10m \ + --burst-limit 200 \ + --qps 100 - name: Report deploy outcome if: always()