jakman85andClaude Opus 4.8
38fcfadbf0
Add platform/vpn-egress/egress-steering.yaml — a CiliumEgressGatewayPolicy that steers homelab.keithjackson.dev/egress-class=vpn pods out a gateway node's host tun0 split-tunnel interface, per ADR-0015 (node-level tunnel + Cilium Egress Gateway). Honors all four ADR-0015 invariants: only vpn-class pods are selected (default/internet + node stay on the local/WAN path), RFC1918 + cluster ranges are excludedCIDRs so only public internet is tunneled and tun0 is never a default route, and the host nftables kill-switch (Ansible) fails vpn-class CLOSED while internet-class fails OPEN. Interface contract shared verbatim with the parallel Ansible host-tunnel role: node label homelab.keithjackson.dev/egress-gateway=true, interface tun0, client label homelab.keithjackson.dev/egress-class=vpn. Cilium Egress Gateway prerequisites confirmed enabled (egressGateway.enabled, bpf.masquerade, kubeProxyReplacement all true, [parity]) — no HelmRelease change. Intentionally NOT added to platform/vpn-egress/kustomization.yaml: the datapath stays out of the runtime until the live tunnel exists and the egress-class / vpn-killswitch conformance tests pass (README rule; DoD). Gluetun is retained as the validated fallback until then. Serves R-NET-05/06/07. Co-Authored-By: Claude Opus 4.8 <[email protected]>
home-network-k3s-impl
Implementation of the home k3s + Longhorn platform. This repo holds the reconciled artifacts
(Flux config, Kustomize overlays, KubeVirt/Helm manifests, ServiceDefinitions, Kyverno policies,
Chainsaw conformance tests, CI). It is driven by — and subordinate to — the read-only
specification at ../home-network-k3s.
Rules (from the spec — non-negotiable)
- The spec is read-only. Never modify anything under
../home-network-k3s. Implement against it; escalate spec problems, don't edit them (specAGENTS.md§11, R-TEST-06). - Done = a green, reproducible, requirement-tagged conformance test — never "merged," never a
manual demo (spec
docs/14,agents/definition-of-done.md). - No work on
main. Every change is a feature branch merged intomain(specCONTRIBUTING.md). - No plaintext secrets — SOPS-encrypted only (spec
docs/07). - Phase discipline — only build what the active roadmap phase authorizes (spec
roadmap/phases.md).
Layout
platform/ platform services (Flux HelmReleases/Kustomizations): cilium, longhorn,
cert-manager, externaldns, gateway, monitoring, velero, kubevirt,
image-automation, keycloak, oauth2-proxy, kyverno/
apps/ application workloads, one dir per catalog service
catalog/ ServiceDefinition entries (the onboarding surface)
schemas/ ServiceDefinition JSON Schema + renderer contract
clusters/ Flux entrypoints + dev/ and prod/ overlays
conformance/ Chainsaw behavior/conformance suite + harness + coverage report
.gitea/ Gitea Actions CI (lint · schema · Kyverno L0 · Chainsaw trigger · merge gate)
Current phase: Phase 0 — Foundations (repo, CI, ServiceDefinition schema, conformance harness, Kyverno L0 gate). No cluster exists yet; Phase 1 (cluster bring-up) is not authorized.