410a0be8e395216d527094a83581d3e09ed44da4
Allow the Kubernetes Hermes pod to reach the Docker Swarm socket proxy used for read-only Swarm inspection. The session history shows the established endpoint as `192.168.1.96:2375`; previous direct checks used Docker API `/v1.44/version`, `/version`, `/_ping`, `/services`, and `/volumes`. This PR adds only a narrow egress rule for TCP 2375 to `192.168.1.96/32`. It does not add an environment variable or change the socket proxy's read-only configuration. Reviewed-on: #10 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%