mrcharles
8f1642bf96
Bootstrap a regular (non-ITAR) k3s cluster on cnode1/2/3 with embedded
etcd. All cluster communication — node registration, API server, etcd
peering, flannel VXLAN — runs exclusively over Tailscale IPs. Zero LAN
addresses appear in node status or TLS certificates.
Scripts (k8s/):
- env.sh: shared config (Tailscale IPs, SSH opts, k3s version)
- wipe.sh: remove existing k3s from all cnodes
- install-cp.sh: full bootstrap (cnode1 --cluster-init, then cnode2/3 join)
- join-servers.sh: re-join cnode2/3 only (fixes broken join state)
- post-setup.sh: apply NoSchedule taints, fetch kubeconfig, verify
- verify.sh: 13-point health check (nodes, Tailscale IPs, taints, etcd,
CoreDNS, API server, workload isolation)
- probe-nodes.sh: SSH + Tailscale reachability check
All 3 cnodes are tainted control-plane:NoSchedule so no user workloads
can schedule on the control plane. 13/13 health checks pass.
Docs updated: k8s README TL;DR reflects k3s (not Talos) as the deployed
choice, with Talos preserved for the future ITAR cluster.
💘 Generated with Crush
Assisted-by: Crush:glm-5.2
4.5 KiB
4.5 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.2)
Current State: STABLE
The merged PFVCluster repo is fully operational across provisioning, DNS infrastructure, Proxmox cluster ops, and k8s control plane.
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 Control Plane (k3s HA — LIVE)
- 3-node k3s HA control plane deployed: cnode1/2/3 (v1.36.2+k3s1, embedded etcd)
- All traffic over Tailscale IPs — no LAN IPs in node status or certs
- All 3 cnodes tainted
control-plane:NoSchedule(zero user workloads) - 13/13 health checks pass (verify.sh): nodes Ready, etcd quorum, Tailscale IPs, CoreDNS, API server, workload isolation
- Scripts in
k8s/: wipe, install-cp, join-servers, post-setup, verify - Kubeconfig saved to
~/.kube/config.pfv-k8s(gitignored, embedded certs) - Workers (wnodes) not yet joined to this cluster
- Distro decision: k3s chosen for regular R&D cluster. Talos docs
preserved in
docs/k8s/for future ITAR/classified cluster.
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 workers: Join wnodes to the k3s cluster (agents, not servers)
- k8s: confirm 3 decisions for future Talos/ITAR cluster:
- 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) |
| k8s control plane | 3-node k3s HA (cnode1/2/3), all traffic over Tailscale |
| Production | Cloudron VPS, Reston VA (this cluster is R&D only) |