feat(dns): publish Gateway names to the WAN via in-cluster DDNS
gate / gate (pull_request) Successful in 1m46s
gate / conformance (pull_request) Has been skipped

Gateway-published records now CNAME to wan.${BASE_DOMAIN}, which a
favonia/cloudflare-ddns Deployment keeps at the home WAN's current public
IP. Operator decision: every Gateway-published name goes public; internal
services (controller: none) remain unpublished.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
This commit is contained in:
jakman85andClaude Opus 5.5 committed 2026-10-03 16:59:53 -05:00
1 parent bcb8931b4f
commit a1e808e697
6 files changed
+224 -30

No files matched your search

+2
View File
@@ -8,3 +8,5 @@ resources:
# SOPS-encrypted Cloudflare token (env CF_API_TOKEN) — SAME token as cert-manager, second copy in
# the external-dns namespace. Flux decrypts at reconcile.
- cloudflare-api-token.sops.yaml
# DDNS for `wan.${BASE_DOMAIN}` — the CNAME target every Gateway-published record points at.
- ddns.yaml