coulomb/railiance-apps
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Use websecure-only ingress for coulomb-social HTTP-01
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details

Browse source 
Leave port 80 free for cert-manager solvers (forgejo pattern) so ACME
challenges are not contended by the app router.
This commit is contained in:
tegwick 2026-08-09 23:37:08 +02:00
parent 8eca75735d
commit 3f3ffd279f
1 changed files with 3 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

4
manifests/coulomb-social-ingress.yaml
View file

@ -8,7 +8,9 @@ metadata:
namespace: coulomb-social namespace: coulomb-social
annotations: annotations:
cert-manager.io/cluster-issuer: letsencrypt-prod cert-manager.io/cluster-issuer: letsencrypt-prod
traefik.ingress.kubernetes.io/router.entrypoints: web,websecure # websecure only (forgejo pattern): leave HTTP free for cert-manager HTTP-01
# solvers. TLS app traffic stays on 443; ACME challenge uses solver ingress on 80.
traefik.ingress.kubernetes.io/router.entrypoints: websecure
traefik.ingress.kubernetes.io/router.tls: "true" traefik.ingress.kubernetes.io/router.tls: "true"
spec: spec:
ingressClassName: traefik ingressClassName: traefik