bluejay/bluejay-infra
1
0
Fork 0
Code Issues Pull Requests 15 Actions Packages Projects Releases Wiki Activity

ops(github-runner): scale tts-reader runner to 0 (crash-looping, memory relief)

Browse Source 
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) <noreply@anthropic.com>
This commit is contained in:
Andrew Stoltz
2026-06-16 11:27:40 -05:00
parent b28ab73a19
commit 6950010ea4
1 changed files with 6 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
apps/github-runner/github-runner.yaml
View File

@@ -1698,7 +1698,12 @@ metadata:
flowercore.io/runner-repo: tts-reader flowercore.io/runner-repo: tts-reader
flowercore.io/github-repo: FlowerCore.TtsReader flowercore.io/github-repo: FlowerCore.TtsReader
spec: 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: selector:
matchLabels: matchLabels:
app.kubernetes.io/name: github-runner-tts-reader app.kubernetes.io/name: github-runner-tts-reader