## 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>
See commit 1af4832. Removes the broken global redirect that exposed internal :8443, pins TLS routes to websecure, and adds a dedicated web redirect middleware so ACME HTTP-01 remains isolated.
---------
Co-authored-by: Hermes Agent <hermes@localhost>
Reviewed-on: #22
Reviewed-by: admin <rudolfss13@gmail.com>
Co-authored-by: hermes <rudolfss13+hermes@gmail.com>
## Summary
- add the declarative K3s `HelmChartConfig` for Traefik `web`/`websecure`
- expose TCP 80/443 and configure the `letsencrypt` HTTP-01 resolver
- persist `/data/acme.json` through a PVC
- add TLS routing annotations and host lists for the shared public Ingress and Hermes Ingress
- document the router cutover, verification procedure, and separate DEC-012 decision
## Scope
This PR contains the traffic configuration and documentation. It does not execute `kubectl apply`, change Keenetic, issue certificates, or commit credentials.
## Required operator input before apply
- direct WAN TCP 80 and 443 forwarding to 192.168.1.114
- the real Let's Encrypt registration email, inserted through the approved values/secret workflow rather than invented in Git
- final review of the installed Traefik chart values and PVC/storage behavior
## Verification
- `git diff --check` passed
- base: `e084ce4ecf39f19d08ec97fee852f59310e0cdbb`
- head: `4f70885`
Related decision: `docs/decisions/2026-11-21-traefik-tls-http01.md`
---------
Co-authored-by: Hermes Agent <hermes@localhost>
Reviewed-on: #21
Reviewed-by: admin <rudolfss13@gmail.com>
Co-authored-by: hermes <rudolfss13+hermes@gmail.com>