platform-engineer-agent/k3s-cluster
1
0
Fork 0
forked from roger/k3s-cluster
Code Pull Requests Activity

fix hermes api not being reachable

Browse Source
This commit is contained in:
Roger Oriol
2026-07-26 17:08:27 +02:00
parent 575c7bf9e0
commit 5bb1066d0d
2 changed files with 10 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
home-manager/deployment.yaml
View File

@@ -109,6 +109,11 @@ spec:
# to the agent as an OpenAI-compatible endpoint.
- name: API_SERVER_ENABLED
value: "true"
# Bind the gateway API on all interfaces so other pods can reach it
# via the Service (default is 127.0.0.1/loopback, which is unreachable
# cross-pod). Auth is still enforced via API_SERVER_KEY.
- name: API_SERVER_HOST
value: "0.0.0.0"
# NOTE: API_SERVER_KEY comes from the hermes-env Secret (via envFrom)
# and is also seeded into /opt/data/.env by the init container. Clients
# (e.g. Open WebUI) authenticate with `Authorization: Bearer <key>`.

5
platform-engineer/deployment.yaml
View File

@@ -138,6 +138,11 @@ spec:
# to the agent as an OpenAI-compatible endpoint.
- name: API_SERVER_ENABLED
value: "true"
# Bind the gateway API on all interfaces so other pods can reach it
# via the Service (default is 127.0.0.1/loopback, which is unreachable
# cross-pod). Auth is still enforced via API_SERVER_KEY.
- name: API_SERVER_HOST
value: "0.0.0.0"
# NOTE: API_SERVER_KEY comes from the hermes-env Secret (via envFrom)
# and is also seeded into /opt/data/.env by the init container. Clients
# (e.g. Open WebUI) authenticate with `Authorization: Bearer <key>`.