jakman85andClaude Opus 4.8
1749603f87
Deploy Homepage (gethomepage) as the apex landing dashboard aggregating links to cluster services, in its OWN non-gating post-platform Flux Kustomization (clusters/base/homepage.yaml, dependsOn platform-config, wait:false) — mirrors headlamp/oauth2-proxy so a leaf UI can never gate the platform chain. - platform/homepage/: plain manifests (ns, config ConfigMap, Deployment, Service, default-deny+Cilium ingress NP, apex HTTPRoute). Non-root pod, HOMEPAGE_ALLOWED_HOSTS, bundled mdi-* icons (DNS-only egress). - gateway.yaml: add https-apex + http-apex-redirect listeners for the bare apex (the *.home wildcard listener does NOT match it). Apex is already a SAN on the wildcard cert — no new Certificate. - Forward-auth annotated (auth-mode=forward-auth) but NOT enforced: the Gateway ext-authz mechanism is an unbuilt Phase-6 WS-NET TODO (same status as all other forward-auth apps). Flagged as PM follow-up. Gate: lint/l0/render-golden(10/10)/l1 green; conformance skipped (no cluster). Co-Authored-By: Claude Opus 4.8 <[email protected]>
platform/gateway
Gateway API (north-south ingress) implemented by Cilium + the shared HTTPS Gateway and the wildcard TLS certificate.
- Governing ADRs: ADR-0002 — Cilium + Gateway API, ADR-0006 — cert-manager/Let's Encrypt
- Spec: docs/09 — DNS & Ingress
- Serves: R-DNS-01, R-TLS-01
- Owner: WS-NET (+ WS-SEC for the cert)
What this stub is
GatewayClasscilium— Gateway API implemented by Cilium; no separate ingress controller (ADR-0002).Gatewayshared— HTTPS listener on*.home.keithjackson.dev, TLS terminated with the wildcard cert. App HTTPRoutes attach cross-namespace via a namespace label + ReferenceGrant (rendered by WS-APPS from each ServiceDefinition'sexposure).Certificatewildcard-home—*.home.keithjackson.devissued by${ACME_CLUSTER_ISSUER}(staging in dev, prod in prod — R-ENV-02). Makes onboarding certificate-free (ADR-0006 default).
Contract (Issuer + Gateway TLS)
The "Issuer + Gateway TLS" interface (roadmap/workstreams.md): this Gateway + wildcard cert are what
every service's HTTPRoute attaches to. ExternalDNS (../externaldns) publishes the
public records for hostnames routed here. Ingress opens north-south only — it does not relax
east-west default-deny (docs/09).
TODO (later phases)
- Phase 2 (WS-NET): pin the L2-announced ingress VIP / IP pool (Cilium L2 announcement, docs/09); add the HTTP→HTTPS redirect route; confirm the cross-namespace ReferenceGrant pattern with WS-APPS.
- Public exposure is a manual edge port-forward of 80/443 to the Gateway VIP (single SOHO router, docs/09) — a documented manual step, the analogue of the old pfSense exception.