fix(ingress): let Traefik own HTTP-01 challenge path #23

Merged
admin merged 1 commits from hermes/k3s:fix/traefik-http-redirect into main 2026-11-22 22:29:21 +01:00
Member

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.

## 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.
hermes added 1 commit 2026-11-22 22:16:28 +01:00
hermes force-pushed fix/traefik-http-redirect from 8738e3c9d0 to 875a2fd0f1 2026-11-22 22:16:28 +01:00 Compare
admin approved these changes 2026-11-22 22:29:15 +01:00
admin merged commit 0d29c7d7af into main 2026-11-22 22:29:21 +01:00
admin deleted branch fix/traefik-http-redirect 2026-11-22 22:29:21 +01:00
Sign in to join this conversation.
No Reviewers
No labels
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: org1/infra#23