eho/register-referentie
1
0
Fork 0
Code Issues 10 Pull Requests 1 Actions Packages Projects Releases 1 Wiki Activity

docs(arch): ADR-0035 — publish the stack through the existing labs Caddy (closes #177)
CI / lint (pull_request) Successful in 1m45s
Details
CI / k8s (pull_request) Successful in 9s
Details
CI / build (pull_request) Successful in 1m41s
Details
CI / unit (pull_request) Successful in 2m3s
Details
CI / frontend (pull_request) Successful in 2m23s
Details
CI / mutation (pull_request) Successful in 5m39s
Details
CI / verify-stack (pull_request) Skipped
Details

Browse Source 
Records the decision #177 asked for, the other way round: the hypervisor has no
inbound path and the labs Caddy already holds 80/443 and the wildcard cert, so
the portals go through it over a reverse SSH tunnel instead of an in-cluster
edge. Covers keycloakUrl, KC_PROXY_HEADERS and the optional demo OTP autofill.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
not
2026-09-25 15:05:38 +02:00
co-authored by Claude Opus 5.5
parent f4b41aca84
commit 84cea6267e
3 changed files with 111 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/runbooks/kubernetes-talos.md
+2
View File
@@ -403,6 +403,8 @@ upgrade path.
## Publishing through the labs Caddy
Why this route and not an in-cluster edge: [ADR-0035](../architecture/adr-0035-public-access-through-the-labs-caddy.md).
The portals can be reached on real hostnames through the Caddy that already fronts
`*.labs.respellion.tech` (repo `Infra`, `infra/development/`). The chain: