From 8a04ec5cf5b3cfbe966a501ca36f5c40076d2c5c Mon Sep 17 00:00:00 2001 From: Tom Bar Date: Tue, 2 Jun 2026 16:50:09 -0300 Subject: [PATCH] docs(exec-backend): reference upstream hermes-agent PR #37591 The agent-side kubernetes exec backend is contributed upstream in NousResearch/hermes-agent#37591. Reference it from the how-to (Prerequisites + Cross-link) so readers know where the agent-side half lives, why a custom-built image is needed today, and what to track for the stock image to work. Signed-off-by: Tom Bar --- docs/docs/how-to/kubernetes-exec-backend.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/docs/docs/how-to/kubernetes-exec-backend.md b/docs/docs/how-to/kubernetes-exec-backend.md index 599908f..ace0d17 100644 --- a/docs/docs/how-to/kubernetes-exec-backend.md +++ b/docs/docs/how-to/kubernetes-exec-backend.md @@ -14,6 +14,10 @@ create is constrained by a cluster `ValidatingAdmissionPolicy` (VAP). Together, `quantity()` CEL extension). - A hermes-agent image that bundles the `kubernetes` client extra (the agent's `kubernetes_subprocess.ExecutionBackend` driver imports it lazily). + The agent-side backend is proposed upstream in + [NousResearch/hermes-agent#37591](https://github.com/NousResearch/hermes-agent/pull/37591); + until it ships in a tagged release, use an image built from that branch + (e.g. `ghcr.io/undermountaincc/hermes-agent`). - The session-pod VAP installed cluster-wide (see below). The CR's `spec.execBackend: kubernetes` reconciles the per-agent Role / RoleBinding / session SA regardless, but **without the VAP the bare `pods/create` Role @@ -108,4 +112,10 @@ reconcile. The agent-side implementation (the `kubernetes_subprocess` backend, the `TERMINAL_ENV=kubernetes` plumbing, the lazy-loadable Python dep) lives in the upstream [hermes-agent](https://github.com/NousResearch/hermes-agent) -repo. +repo, contributed in +[PR #37591](https://github.com/NousResearch/hermes-agent/pull/37591). This +operator provides the cluster-side half — the per-agent exec RBAC, the +powerless session ServiceAccount, and the session-pod `ValidatingAdmissionPolicy` +that make granting `pods/create` safe. Track that PR for the upstream status; +once it lands in a tagged release, the stock `nousresearch/hermes-agent` image +works without a custom build.