From c44f16e4acee172ab75e7761acf7049315cce361 Mon Sep 17 00:00:00 2001 From: jenkins Date: Tue, 25 Aug 2026 10:10:24 -0300 Subject: [PATCH] fix(hermes): require rpi5 for worker (keep the heavy agent off rpi4) Un-pinning let the scheduler land worker on titan-12 (rpi4). The agent is heavy enough that an rpi4 risks the /api/status slowness that trips its liveness probe - the exact flap we are avoiding. Make hardware=rpi5 a hard requirement so it runs only on rpi5 storage workers (excluding the saturated/known-flaky ones); the scheduler places it on a roomy rpi5 (titan-05). Co-Authored-By: Claude Opus 4.8 Claude-Session: https://claude.ai/code/session_01BvMSXH8VH2tMWXanb8SJdf --- services/hermes/agent-deployment.yaml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/services/hermes/agent-deployment.yaml b/services/hermes/agent-deployment.yaml index 9fce2b2c..578263b6 100644 --- a/services/hermes/agent-deployment.yaml +++ b/services/hermes/agent-deployment.yaml @@ -108,6 +108,12 @@ spec: - key: node-role.kubernetes.io/worker operator: In values: ["true"] + # Require rpi5: the agent is heavy and an rpi4 is slow enough to + # risk tripping the /api/status liveness probe. rpi5 storage + # workers only, excluding the saturated/known-flaky ones. + - key: hardware + operator: In + values: [rpi5] - key: kubernetes.io/hostname operator: NotIn values: [titan-04, titan-06, titan-08, titan-13, titan-14, titan-17, titan-18, titan-19]