jakman85andClaude Opus 4.8
cbc2301b30
Text-only cleanup after the upgrade campaign. Updates stale version strings, prose, and comments to the verified current facts; no Kubernetes behavior or version pins changed except the kubectl toolchain bump (below). Verified facts applied: k3s v1.36.4+k3s1, Debian 13 trixie, Cilium 1.20.1 / Gateway API v1.6.1, Longhorn 1.12.1, node RAM 24 GiB, dedicated virtio2 SSD etcd disk per node, Velero chart 12.x / v1.18, Grafana 13.2.0. - Version strings across infra/ and platform/ READMEs + comments - kubectl toolchain 1.31.4 -> 1.36.4 (devcontainer/ci/conformance versions.env; 1.31 vs a 1.36 cluster exceeded the +-1 skew) - Retired-single-apps-Kustomization refs -> apps-wave-0/1/2 + apps-vms with per-wave SOPS decryption (flux/clusters docs + bootstrap.sh) - COMPLETED/historical banners on the three executed plan docs - Resolved TODO(WS-SEC) markers -> Renovate-maintained ranges - Appended dated DECISIONS-LOG entry (2026-08-30) superseding the 2026-08-26 LIVE STATE line Left as revalidation items (not blind-edited): external-snapshotter v8.2.0 vs 1.36, Cilium ext_authz/forward-auth relevance under 1.20.1, conformance ImageVolume feature-gate assertions under 1.36. Co-Authored-By: Claude Opus 4.8 <[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).