hermes 2c84082e22 feat(hermes): expose dashboard through public ingress (#12)
## 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>
2026-11-18 23:34:55 +01:00
2020-12-02 23:35:47 +03:00
2025-05-16 23:19:05 +02:00
2023-03-11 20:55:38 +01:00
2020-12-02 23:35:47 +03:00
2017-06-08 23:08:24 +03:00
2018-05-02 23:12:40 +03:00
2020-12-02 23:35:47 +03:00
2021-08-19 00:16:56 +03:00
2023-03-11 20:55:38 +01:00
2025-06-02 23:56:25 +02:00
x
2026-11-12 23:08:52 +01:00
2020-12-03 00:22:50 +03:00
2020-12-02 23:35:47 +03:00
2026-11-13 20:24:30 +01:00
2017-11-28 22:58:00 +03:00
2026-10-05 23:54:20 +02:00
2026-11-13 20:24:30 +01:00
2020-12-02 23:35:47 +03:00
2020-12-02 23:35:47 +03:00
2020-12-02 23:35:47 +03:00

Infrastructure repository

See FINDINGS.md for unresolved compliance findings and required follow-up actions.

Manual operations and service documentation

Cluster and production operations

Service documentation

The service-specific Docker documentation remains valid only for services that have not yet been migrated. Update the migration status above and the service documentation when a service moves to Kubernetes.

Repository layout

S
Description
No description provided
Readme
11 MiB
Languages
Python 46.4%
Jinja 32.6%
Shell 14.4%
Dockerfile 6.6%