main
## Problem Let's Encrypt HTTP-01 requests were reaching ordinary Kubernetes HTTP routes instead of Traefik's internal ACME challenge handler. The CA observed backend responses (404/401/403), so Traefik continued serving its default certificate. ## Change - remove the Kubernetes `web` catch-all redirect Ingress and its backend routes; - restore Traefik entrypoint HTTP-to-HTTPS redirect; - set the redirect port explicitly to public `443`, preventing internal `:8443` in `Location`; - keep `web` available for the built-in HTTP-01 challenge router; - update the ingress decision/runbook. ## Verification - `git diff --check` passes; - `kubectl kustomize k3s_rencher/infrastructure/ingress` renders successfully; - rendered resources no longer include the Kubernetes HTTP redirect catch-all; - the Traefik redirect explicitly targets public port `443`. ## Post-merge acceptance Verify externally that HTTP redirects to `https://<host>/` without `:8443`, a real HTTP-01 attempt succeeds, and the served certificate has Let's Encrypt issuer/SANs for all four domains. --------- Co-authored-by: Hermes Agent <hermes@localhost> Reviewed-on: #23 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
- Shared Traefik ingress and HTTPS operations
- Traefik TLS/HTTP-01 decision
- 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%