feat(hermes): expose dashboard through public ingress #12

Merged
admin merged 1 commits from hermes/k3s:feat/hermes-public-ingress into main 2026-11-18 23:34:57 +01:00
Member

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.
## 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.
hermes added 1 commit 2026-11-18 20:20:09 +01:00
admin approved these changes 2026-11-18 23:32:49 +01:00
admin merged commit 2c84082e22 into main 2026-11-18 23:34:57 +01:00
admin deleted branch feat/hermes-public-ingress 2026-11-18 23:34:58 +01:00
Sign in to join this conversation.
No Reviewers
No labels
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: org1/infra#12