From 6950010ea416c3bd5895b93b53f014a7cb70c130 Mon Sep 17 00:00:00 2001 From: Andrew Stoltz Date: Tue, 16 Jun 2026 11:27:40 -0500 Subject: [PATCH] ops(github-runner): scale tts-reader runner to 0 (crash-looping, memory relief) The github-runner-tts-reader pod was crash-looping (329 restarts) and consuming memory on the over-pressured old rke2 cluster (rke2-agent1 ~81%), contributing to Blazor SignalR circuit drops on ttsreader/chat. It provides no working CI in this state. Set replicas: 0 so ArgoCD stops re-creating it; restore to 1 once the runner is fixed or CI moves to a working host. Co-Authored-By: Claude Opus 4.8 (1M context) --- apps/github-runner/github-runner.yaml | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/apps/github-runner/github-runner.yaml b/apps/github-runner/github-runner.yaml index 4109c9c..cdc91e4 100644 --- a/apps/github-runner/github-runner.yaml +++ b/apps/github-runner/github-runner.yaml @@ -1698,7 +1698,12 @@ metadata: flowercore.io/runner-repo: tts-reader flowercore.io/github-repo: FlowerCore.TtsReader spec: - replicas: 1 + # Scaled to 0 2026-06-16: this runner was crash-looping (329 restarts) and + # consuming memory on the over-pressured old cluster (agent1 ~81%), which was + # contributing to Blazor circuit drops on ttsreader/chat. It provides no + # working CI in this state. Restore to 1 once the runner is fixed (or the repo + # CI moves to the GX10 / a working runner). + replicas: 0 selector: matchLabels: app.kubernetes.io/name: github-runner-tts-reader