  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 |
|
|
kacerrandClaude Opus 5.5
|
5fd998c5f9
|
Initial import: phase docs, configs, Claude conventions
Phase 1-3 runbooks and design notes, version pins, config templates,
project-history conventions, cluster-inspector read-only credentials setup.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
2026-09-27 00:58:52 +02:00 |
|