jakman85andClaude Opus 4.8
ca982864fc
Un-suspend deadlocked: the single platform Kustomization applies HelmReleases
(which register CRDs) AND custom resources of those CRDs (ClusterIssuer,
Certificate, Kyverno ClusterPolicies) in ONE pass. Flux's server-side apply
fails atomically ('no matches for kind ClusterIssuer') → nothing installs, so
the CRD-registering HelmReleases never run either. Classic ordering deadlock.
Fix (flux2 controllers/configs pattern, applies to dev+prod equally — no
R-ENV-02 divergence): add a platform-config Flux Kustomization (dependsOn
platform, wait) carrying the CRs; platform keeps only the controllers.
- New clusters/base/platform-config.yaml (path ./platform-config, substituteFrom
cluster-vars, no decryption — no SOPS content); wired into base + apps now
dependsOn platform-config (transitively waits for platform).
- platform-config/ references the CR files IN PLACE via ../platform/... (Flux
builds LoadRestrictionsNone; Kyverno policies must stay under platform/kyverno/
for the CI L0 gate). CR resources dropped from the platform
component kustomizations (cert-manager, gateway, kyverno).
- Authored the missing Cilium L2 resources (were only a TODO): CiliumLoadBalancerIPPool
(dev NAT 10.73.0.240-.250) + CiliumL2AnnouncementPolicy (ens*), so Gateway
LoadBalancer listeners get a VIP. Prod range must be parameterized later.
Verified: platform build has zero CRs; platform-config build has 2 ClusterIssuers,
6 ClusterPolicies, Certificate, Gateway, both Cilium L2 CRs; dev/prod build; gate PASS.
Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
platform/cert-manager
cert-manager — trusted TLS via Let's Encrypt, ACME DNS-01 (Cloudflare).
- Governing ADR: ADR-0006 — TLS: cert-manager + Let's Encrypt (DNS-01)
- Spec: docs/08 — TLS & Certificates, docs/09 — DNS & Ingress
- Serves: R-TLS-01/02/03, R-DNS-01
- Owner: WS-SEC
What this stub is
Flux HelmRelease + two ClusterIssuers (letsencrypt-staging, letsencrypt-prod — both
mandated by ADR-0006). DNS-01 against the keithjackson.dev zone validates domain control without
exposing the service (works for internal-only services, R-TLS-03) and enables the wildcard
*.home.keithjackson.dev cert defined in ../gateway.
Contract (Issuer + Gateway TLS)
Part of the "Issuer + Gateway TLS" interface (roadmap/workstreams.md, WS-SEC + WS-NET): the wildcard
Certificate (in gateway/) references the issuer named by ${ACME_CLUSTER_ISSUER} and its secret
is consumed by the Gateway HTTPS listener.
Secrets
The Cloudflare API token is referenced by name (cloudflare-api-token) and committed
SOPS-encrypted (WS-SEC, OQ-4, ADR-0007). No plaintext token in git.
TODO (later phases)
- OQ-4 (resolved to Cloudflare): WS-SEC provisions the scoped Cloudflare token, SOPS-encrypted.
- Set the ACME account email.
- Phase 2 (WS-SEC): issue the wildcard cert; prove a trusted, non-self-signed cert at
*.home.keithjackson.dev(R-TLS-01/03, Phase-2 exit gate).