2c84082e22b8fc66f31696c1e7e76630085cc665
## 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>
Infrastructure repository
See FINDINGS.md for unresolved compliance findings and required follow-up actions.
Manual operations and service documentation
Cluster and production operations
- K3s installation and health operations
- GitOps and Flux bootstrap
- Legacy production setup
- Legacy Docker Compose operations
Service documentation
- Nextcloud operations
- Hermes Squid operations
- Anywherelan deployment
- Beszel stack
- Gitea runner stack
- Hermes stack
- Hermes Agent Kubernetes deployment
- Immich stack
- Lampa stack
- NetBird deployment
- VS Code server stack
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
- k3s_rencher/ — Kubernetes and Flux resources.
- connectivity_tester/ — connectivity tester image and tests.
- poc/ — legacy and experimental service deployments.
- nextcloud/ and hermes_squid/ — legacy service deployments.
- roles/ — legacy Ansible roles retained during migration.
- scratches/ — historical experiments; not production configuration.
Languages
Python
46.4%
Jinja
32.6%
Shell
14.4%
Dockerfile
6.6%