kacerrandClaude Opus 5.5 5e5b6c506a lab1: 2 GiB workers, CAPMOX memory overcommit, CA install (Step 6), future-tasks ...

Owner's pending work, committed ahead of the pv1-2 change it underlies:
- lab1.yaml: worker template lab1-worker-2g (2048 MiB, decision #16), MD rollout
  maxSurge 0 / maxUnavailable 1, ProxmoxCluster schedulerHints.memoryAdjustment 160 (#17)
- cluster-autoscaler values: RBAC for proxmoxmachinetemplates, aggressive scale-down
  profile, Cilium startup-taint; runbook Steps 4-7 and troubleshooting rows
- inflate test pods 512Mi; decisions #16/#17; session note on the memory overcommit
- docs/future-tasks.md convention (CLAUDE.md, README) with the namespace-per-cluster task
- AGENTS.md; allowlist entries in .claude/settings.json

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-09-30 11:05:39 +02:00

..

2026-09-26-2355-history-conventions.md

Initial import: phase docs, configs, Claude conventions

2026-09-27 00:58:52 +02:00

2026-09-27-1112-lab1-first-review.md

lab1: pin cilium-operator to the control plane; Step 5 verified

2026-09-28 09:23:41 +02:00

2026-09-28-1007-capmox-memory-overcommit.md

lab1: 2 GiB workers, CAPMOX memory overcommit, CA install (Step 6), future-tasks

2026-09-30 11:05:39 +02:00

2026-09-29-2311-pve-two-node-cluster.md

Plan: lab1 workers on pv1-2 via per-node template copy

2026-09-29 23:16:49 +02:00