bastion/deploy/k3s/configmap.yaml

apiVersion: v1
kind: ConfigMap
metadata:
  name: bastion-config
  namespace: lab-infra
data:
  HTTP_PORT: "8080"
  DOMAIN: "ad.itaz.eu"
  FEDORA_VERSION: "43"
  DHCP_MODE: "proxy"
  TIMEZONE: "Europe/London"
  LOCALE: "en_GB.UTF-8"
  LABD_URL: "http://labd.lab-system.svc.cluster.local:3100"
feat: release pipeline, k3s manifests, infra k3s bootstrap - scripts/release.sh: full release orchestration (build, publish, install) - deploy/k3s/: Deployment, ConfigMap, PVC, Namespace with kustomize hostNetwork for dnsmasq, NET_ADMIN caps, local-path PVC - Infra role gets /var/lib/rancher partition (20GB, preserved on reprovision) for k3s etcd data persistence across reinstalls - Infra %post installs k3s server (INSTALL_K3S_SKIP_START=true) - 5 new kickstart tests (27 total) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> 2026-03-17 21:56:39 +00:00			`apiVersion: v1`
			`kind: ConfigMap`
			`metadata:`
			`name: bastion-config`
			`namespace: lab-infra`
			`data:`
			`HTTP_PORT: "8080"`
			`DOMAIN: "ad.itaz.eu"`
			`FEDORA_VERSION: "43"`
			`DHCP_MODE: "proxy"`
			`TIMEZONE: "Europe/London"`
			`LOCALE: "en_GB.UTF-8"`
feat: install logging, error trapping, PXE/ISO integration tests Kickstart installs on real hardware failed silently — no error reporting, only 3 progress callbacks, zero log streaming. This overhaul makes every install fully observable. Kickstart improvements: - Error trapping in %pre and %post (trap ERR sends failure details to bastion) - 12+ granular progress stages (was 3): SSH, hostname, k3s prep, EFI boot, metadata - Background log streamer: tails %post output and batch-sends to /api/log - bastion_log() function for explicit log lines from kickstart scripts Bastion API: - POST /api/log — receives raw log lines from kickstart (single or batch) - InstallLogBuffer — per-MAC ring buffer (2000 lines) + file persistence - GET /api/logs/:mac — now returns log_lines + log_total alongside stages - SSE /api/logs/:mac/follow — uses named events (event: stage vs event: log) - Progress events forwarded to labd via bastion-progress WebSocket message - Post-provision k3s logs routed through progressBus (was console-only) dnsmasq fixes found during VM testing: - HTTP Boot filename: ipxe-real.efi → ipxe.efi (leftover from old 2-stage approach) - pxe-service directives: only in proxy mode (breaks OVMF PXE in full mode) - PXEClient vendor class echo for UEFI firmware compatibility Integration tests: - PXE boot test: blank UEFI VM → dnsmasq → HTTP Boot → iPXE → bastion → install - ISO boot test: blank VM boots from bastion-generated ISO → same flow - Shared helpers: pxe-network (no DHCP, nftables fix), pxe-vm (UEFI + ISO boot) - test-provision.sh: runs both PXE + ISO tests with prerequisite checks - 250GB sparse QCOW2 disk (LVM layout needs ~204GB) 201 unit tests passing (11 new). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> 2026-03-26 22:26:33 +00:00			`LABD_URL: "http://labd.lab-system.svc.cluster.local:3100"`