fix(hermes): target Talos nodes by name in SOUL.md #1381

Merged
k.renner merged 1 commits from fix/hermes-soul-talos-node-names into main 2026-10-19 09:28:34 +00:00
Member

SOUL.md told the agent to take node InternalIPs from kubectl get nodes -o wide, but the hermes ServiceAccount cannot list nodes (Forbidden). talosctl takes node names instead: talosctl -n k8s-2 get members and talosctl -n k8s-1,k8s-2,k8s-3 version both succeed from the hermes pod. One-line change; the kustomization builds.

`SOUL.md` told the agent to take node InternalIPs from `kubectl get nodes -o wide`, but the `hermes` ServiceAccount cannot list nodes (`Forbidden`). talosctl takes node names instead: `talosctl -n k8s-2 get members` and `talosctl -n k8s-1,k8s-2,k8s-3 version` both succeed from the hermes pod. One-line change; the kustomization builds.
hermes-bot added 1 commit 2026-10-19 09:27:54 +00:00
fix(hermes): target Talos nodes by name in SOUL.md
ci/woodpecker/pr/ci-scripts-test Pipeline was successful
review-bot skipped: closed
ci/woodpecker/pr/ci-manifests-test Pipeline was successful
f76b638dec
The hermes ServiceAccount cannot list nodes, so the InternalIP lookup
via kubectl get nodes failed (Forbidden). talosctl accepts node names
through the talos.default endpoint: talosctl -n k8s-2 get members and
-n k8s-1,k8s-2,k8s-3 version both succeed from the hermes pod.
k.renner merged commit 4b574b77bc into main 2026-10-19 09:28:34 +00:00
Sign in to join this conversation.