From 500741020a94de63cade5056b20dadd0774c39a0 Mon Sep 17 00:00:00 2001 From: jenkins Date: Tue, 25 Aug 2026 10:25:54 -0300 Subject: [PATCH] fix(hermes): revert hard rpi5 requirement (it stranded worker) Requiring rpi5 while the historical hostname exclusion list removes the very rpi5 nodes that currently have headroom (titan-04/06) left only loaded rpi5s (titan-05/07/11), so the agent could not schedule and worker went down. Revert to rpi5-PREFERRED (soft) so it schedules again; proper rpi5 placement needs the exclusion list refreshed against current node health/capacity, tracked separately. 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 deletions(-) diff --git a/services/hermes/agent-deployment.yaml b/services/hermes/agent-deployment.yaml index 578263b6..9fce2b2c 100644 --- a/services/hermes/agent-deployment.yaml +++ b/services/hermes/agent-deployment.yaml @@ -108,12 +108,6 @@ 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]