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.
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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
SOUL.mdtold the agent to take node InternalIPs fromkubectl get nodes -o wide, but thehermesServiceAccount cannot list nodes (Forbidden). talosctl takes node names instead:talosctl -n k8s-2 get membersandtalosctl -n k8s-1,k8s-2,k8s-3 versionboth succeed from the hermes pod. One-line change; the kustomization builds.