Public: anyone can read this; nobody can change it.

workbenchthis machine

/goal /ultracode-workflows [DOM-1a] public ACME TLS for the platform domain (letsencrypt-dns01 ClusterIssuer + public wildcard cert) #24

Closed opened this view on origin

Closed without the crew

opened this view on origin

Track/Wave: DOM-1a · Wave M1 · Size M Repos: gitops, mitosis Depends on: none

Why

For the first client the operator controls DNS, so the MVP does NOT need self-serve domain tooling — it needs one thing: a public, browser-trusted wildcard cert for the platform domain, replacing the private plat-local-ca-issuer every cert chains to today (gitops has NO ACME issuer at all).

Scope

A letsencrypt-dns01 DNS-01 ClusterIssuer + sops-sealed DNS-provider token under clusters/local/platform/letsencrypt/ (DNS-01 so it supports wildcards and works before traffic is routed); issue a public *.<platform-domain> wildcard Certificate so every app under the platform suffix is instantly browser-trusted with ZERO per-app overlay change. acme-staging FIRST, flip to prod after E2E. mitosis: confirm the sealed DNS token flows through fork_regen_secrets/fork_verify_all_sealed; gate the ACME path behind the CUTOVER_TUNNEL-style public-edge opt-in so a purely-local daughter keeps the internal CA. This is exactly "PR 1" of the self-serve-custom-domains proposal.

Acceptance

On a germinated public daughter, an app under *.<platform-domain> serves a leaf that openssl s_client and a stock browser trust as chaining to Let's Encrypt (not plat-local-ca).

Notes

Gitops-only render — NOT on the server.ts overlay seam. Seam C: adds one include line to platform/kustomization.yaml.

--- Part of the First Client Deploy → Governance roadmap. The owning agent may recurse into its own subagent team (ultracode workflow) if the task warrants. Honor the seam-serialization: land on a shared seam by rebase, and don't start a seam position until the prior one has merged.

commented

Build note (from DOM-1a gitops PR plat/gitops#3): the gitops half is done, but the mitosis-side sub-scope changed. fork_regen_secrets enumerates sealed secrets EXPLICITLY (no generic reseal loop) and fork_verify_all_sealed rejects any sops-blocked file it cannot decrypt with the fork key — so a genesis-sealed cloudflare-dns-api.yaml would ABORT daughter germination. PR#3 therefore ships the token unsealed with a placeholder (germination-safe). Remaining mitosis work for DOM-1a: add the Cloudflare DNS token to the fork_regen_secrets enumeration + fork_verify_all_sealed (bin/lib.sh, seam A) so daughters seal it per-fork, and gate ACME behind the CUTOVER_TUNNEL public-edge opt-in. Will land in the seam-A chain.

commented

Code complete + merged (gitops#3 issuer/wildcard + mitosis fork-reseal #53). Activation needs a seed refresh carrying the letsencrypt component + operator CLOUDFLARE_DNS_API_TOKEN at germination + issuer staging→prod flip. Live browser-trusted-TLS validation happens at the real Hetzner deploy. Note: with Cloudflare Tunnel the browser already gets a trusted CF edge cert (Full mode), so DOM-1a is Full-Strict origin hardening, not a first-deploy blocker.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs