## What changed - replace the broken in-cluster Nginx UI deployment with a Traefik Ingress for `hermes.rudolf.keenetic.link`; - route the Ingress to the existing `hermes` Service on its named `dashboard` port (`9119`); - allow only the live Traefik pods in `kube-system` to reach Hermes port `9119`; - remove the UI Nginx capability failure path (`setgid(101) Operation not permitted`); - remove the stale UI middleware/sidecar definition from the Hermes kustomization so Flux can prune it; - document the router mapping and verification path. ## Root cause observed in the cluster The live UI returned `502 Bad Gateway`. The deployed UI sidecar had Nginx workers failing with `setgid(101) Operation not permitted`, while the Ingress was targeting the sidecar path and referenced a middleware that Traefik could not resolve. The direct application Service already exposes the dashboard and WebSocket endpoint on port `9119`, so the sidecar is unnecessary. ## Router Keep the public mapping: `hermes.rudolf.keenetic.link` → `xu4_lan` (`192.168.1.114`) → HTTP `80`. Do not forward to the Kubernetes Service port `9119` or to a Tailscale address from the router. The router forwards to the Kubernetes ingress entrypoint; the Kubernetes Ingress selects the `hermes` Service. ## Verification - base branch is current `org1/infra:main`; - `git diff --check` passes; - no conflict markers are present in tracked files; - live rollout verification remains pending until Flux reconciles this PR, after which verify the Ingress, Traefik route, Service endpoints, and external URL. Reviewed-on: #12 Reviewed-by: admin <rudolfss13@gmail.com> Co-authored-by: hermes <rudolfss13+hermes@gmail.com>
1.6 KiB
Hermes Agent
This deployment runs the Hermes Agent gateway and its Nginx dashboard reverse proxy in Kubernetes with persistent state.
Hermes is a single gateway process; Telegram, the dashboard, scheduled jobs, and persisted sessions share the same pod.
Credentials
Create hermes-credentials in the hermes namespace with the credentials
appropriate for the selected model provider:
kubectl -n hermes create secret generic hermes-credentials \
--from-literal=HERMES_DASHBOARD_BASIC_AUTH_USERNAME='<dashboard user>' \
--from-literal=HERMES_DASHBOARD_BASIC_AUTH_PASSWORD='<dashboard password>'
Do not commit this Secret; supply it through the cluster's secret-management workflow.
Hermes egress allows public IPv4 destinations while blocking:
192.168.0.0/24192.168.1.0/24172.0.0.0/8100.0.0.0/8
The policy is defined in network-policy.yaml.
Migration
See Swarm to K3s migration for placement, volume, and cutover instructions.
Deploy
Render and inspect the manifests, then let Flux reconcile them:
kubectl kustomize k3s_rencher/apps/hermes
kubectl apply -k k3s_rencher/apps/hermes
kubectl -n hermes rollout status deployment/hermes
The dashboard is exposed through the cluster Traefik Ingress at
hermes.rudolf.keenetic.link. The Ingress routes to the hermes Service on
port 9119; Traefik is allowed to reach that port by the namespace NetworkPolicy.
The router must keep the public web application entry pointed at
xu4_lan (192.168.1.114) on HTTP port 80. Do not point the router at the
Kubernetes Service port 9119 or at a Tailscale node address.