mrcharles
174deea2a9
Author the docs/k8s/ directory capturing the pfv-k8s control-plane design:
- README.md: TL;DR of all decisions (distro, runtime, cnode count, admin
access, identity, tenancy, registry, storage)
- DISTRO-DECISION.md: Talos vs k3s analysis. Recommend Talos because the
ITAR/classified requirement makes its immutable, API-only, measured-boot
posture structurally easier to certify than SCAP-hardened Debian. k3s was
only ever a plan (no cluster deployed), so cutover cost is ~zero.
- ARCHITECTURE.md: target arch with mermaid diagrams covering control
plane, LAN-only network with Tailscale subnet-router admin, Cilium CNI,
OIDC to Keycloak, per-tenant vcluster isolation (incl. ITAR tenant),
Harbor pull-through cache on D3 SSD, bootstrap sequence, and DR.
Gardening: register docs/k8s/ in docmap.md, update STATUS.md with the new
k8s section and the three pending user decisions (cnode count, host spread,
Tailscale pattern).
💘 Generated with Crush
Assisted-by: Crush:glm-5.2
4.1 KiB
4.1 KiB
Project Status
Human read-only. Agents maintain this file automatically after each work session. Do not edit by hand — the next agent run will overwrite it.
Last updated: 2026-07-28 by Crush (GLM-5)
Current State: STABLE
The merged PFVCluster repo is fully operational across provisioning, DNS infrastructure, and Proxmox cluster ops.
Completed Work
Server Provisioning (validated on sectestbed-sandbox)
- SetupNewSystem.sh deploys end-to-end to rc=0 (Debian 13 trixie)
- Security hardening: SSH, SCAP-STIG, Wazuh, 2FA (SSH+Cockpit+Webmin)
- NTP: redundant pfv-netinfra-01/02 (192.168.3.252/253), synced stratum 3
- DNS resolv.conf: managed static file pointing at netinfra pair
- Test suite: 5 tests (framework, safe-download, 2fa, https, system-req)
- VM validation harness: git-based deploy + auto-rollback + guest-agent access
DNS Cluster (pfv-netinfra-01/02)
- Production Technitium config replicated from tailscale-router (read-only)
- 124 zones on both nodes (knel.net + reverse DNS)
- pfv-netinfra-01 = PRIMARY, pfv-netinfra-02 = SECONDARY
- Zone replication via rsync systemd timer (every 60s)
- Credentials + 2FA replicated identically to production
- Both LAN IPs resolve knel.net device names + recurse externally
Proxmox Cluster Ops
- 5 of 7 hosts fully performance-tuned (tsys1/3/6/7/9)
- Fleet audit complete (PROJECT.md has ground truth)
- tsys4: blocked on PCIe NIC + RAM install
- tsys5: blocked on 2nd ethernet cable + NVMe install
- tsys2: pending rebuild from Win10 to Proxmox
Kubernetes Architecture (docs authored, pending implementation)
docs/k8s/created: README, DISTRO-DECISION, ARCHITECTURE- Distro decision: Talos Linux (over k3s), driven by ITAR/classified requirement. Immutable + API-only + measured-boot = structurally stronger compliance posture than SCAP-hardened Debian.
- Target arch documented: 3 cnodes (local-lvm boot), Cilium CNI, vcluster per tenant, Harbor pull-through cache on D3 SSD, OIDC→Keycloak (Cloudron), Tailscale subnet-router for admin (cluster nodes LAN-only, zero egress).
- 3 decisions pending user confirm (see Pending below)
Repo Merge
- KNELServerBuild merged into PFVCluster (history preserved)
- Directory structure reorganized (provisioning/, tests/, perf/, docs/)
- All docs gardened: links fixed, stale refs removed, tailscale.md updated
Known Issues
| Issue | Impact | Status |
|---|---|---|
| Technitium AXFR uses port 53 (occupied by Pi-hole) | Zone transfer via rsync instead of native AXFR | Workaround in place |
download.proxmox.com unreachable from sandbox VM |
2 validation tests warn (environmental) | Not a code issue |
| tsys4/5 hardware pending | Perf tuning incomplete on 2 hosts | Waiting on physical install |
Pending (next session priorities)
- k8s: confirm 3 decisions before bootstrap:
- Cnode count: 3 (recommended) vs 5
- Cnode host spread: tsys9 + tsys1 + tsys3 (recommended, 3-host, local-lvm)
- Tailscale pattern: subnet router on
tailscale-router(recommended)
- Provisioning: add
tailscale up --accept-dns=falseafter resolv.conf deploy - DNS: verify Pi-hole forwards knel.net to local Technitium on both nodes
- Perf: complete tsys4/5 tuning after hardware install (Friday)
- tsys2: rebuild from Win10 to Proxmox (k8s-dedicated host)
- k8s deferred topics (tracked for future sessions): ETL tooling (GDAL/PostGIS/xarray/Dask → RWX vs RWO), HPC scheduler (Argo/Volcano), per-tenant vcluster policy templates, solar-aware scale-out
Infrastructure Summary
| Component | Details |
|---|---|
| Proxmox hosts | 7 standalone PVE, managed via PDM |
| DNS primary | pfv-netinfra-01 (192.168.3.252) — Technitium + Pi-hole |
| DNS secondary | pfv-netinfra-02 (192.168.3.253) — Technitium + Pi-hole |
| DNS production | tailscale-router (read-only source of truth) |
| NTP | pfv-netinfra-01/02 (redundant, LAN IPs, stratum 2/3) |
| Sandbox VM | sectestbed-sandbox (VMID 6000 on pfv-tsys5) |
| Backup | Proxmox Backup Server (PBS) |
| Production | Cloudron VPS, Reston VA (this cluster is R&D only) |