[Gerrrt]

What changed

garuda's disk_gib in tofu/guests.tf goes from 80 to 120. build-the-analyst-workstation.md gets the new size in its §0 table and §2 room check, plus a new §14, Grow its disk. There's a changelog entry for 2026-11-09.

Why

GuestDiskWillFillIn24h paged for garuda on 2026-11-08. Nothing was filling. / stepped from 51.6 to 57.2 GiB between 21:24 and 21:44 UTC and stayed flat afterwards, and the alert's six-hour window read that one step as a climb of 1.2 GiB an hour.

The step was the OpenVAS database (ADR-0093). /var/lib/postgresql is 25 GB: one PostgreSQL 18 cluster holding the 24 GB gvmd database and a 1 GB pg_wal, which is PostgreSQL's normal floor. Docker uses under 1 GB. With 16 GB free, the next feed sync or large scan would page again.

Refs #921, ADR-0093.

Blast radius

garuda (VMID 162) alone. The provider grows a disk in place and online, and / has been the last partition since #1128, so the guest takes the space without a reboot. large_data had about 357 GiB free on 2026-11-09 (59% written of 876 GiB), so 40 GiB more of thin allocation is within its room.

• No change to network segmentation or firewall rules
• No new port published to a VLAN that could not already reach the service
• No credential added outside secrets/*.sops.yaml

Verification

• make validate passed. Five checks were skipped as host-specific: four need the deployment checkout, and the backup-offsite tmpfs check can't run here.

• scripts/lint.sh passed, tofu included, with every tool pinned.

• scripts/check_docs.py passed.

• I did not run tofu plan: the state and Proxmox credentials are on phoenix. Before applying, the targeted plan there must read 0 to add, 1 to change, 0 to destroy, and the change must be the disk's size alone (§14 step 2).

• make validate passes

• Deployed to the lab and confirmed working. After merge: §14 steps 2 and 3 on phoenix and garuda.

• Docs updated (docs/, service README, or docs/roadmap.md)

🤖 Generated with Claude Code

[Copilot]

🟡 Changes recommended

The runbook’s §4 first-boot checks still describe an 80 GB disk and 16 GB of extra space, conflicting with the new 120 GB setting that also applies to fresh clones.

1 open issue

• Update §4 disk-space checks for the 120 GB setting · New

What changed in this PR

This PR increases garuda’s declared disk allocation from 80 to 120 GB to accommodate OpenVAS data growth and documents the online expansion procedure. Deployment remains pending.

Changes:

• Increase garuda’s OpenTofu disk size by 40 GB.
• Update sizing guidance and add targeted plan/apply and guest filesystem expansion steps.
• Record the disk alert investigation and capacity change in the changelog.

File	Description
tofu/​guests.tf	Set garuda’s disk allocation to 120 GB.
docs/​runbooks/​build-the-analyst-workstation.md	Update sizing and document online disk expansion.
docs/​changelog.md	Record the alert investigation and planned expansion.

_{Review effort: Balanced}