6a7ad7e235023afab4cbafd06c815e3afb601a98
The merged public Ingress was created as `hermes`, while a legacy `hermes-ui` Ingress with the same host remained in the cluster outside the current Flux inventory. This creates two routes for the same host. Reuse the existing `hermes-ui` resource name so Flux updates it in place and prunes the inventory-managed `hermes` resource, leaving one route for `hermes.rudolf.keenetic.link`. Reviewed-on: org1/infra#13 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%