Remove the 600Mi memory limit on the local Postgres Deployment. With shared_buffers=384MB + max_connections=300 the pod was being repeatedly OOMKilled under real workloads, leaving clients with intermittent connect: connection refused. Keep the 400Mi request for scheduling.
Add document to the seeded database list in initdb.sh.
On a fresh cluster (./setup), verify the document database is created (requires empty data/postgres/)
## Summary
- Remove the 600Mi memory limit on the local Postgres Deployment. With `shared_buffers=384MB` + `max_connections=300` the pod was being repeatedly OOMKilled under real workloads, leaving clients with intermittent `connect: connection refused`. Keep the 400Mi request for scheduling.
- Add `document` to the seeded database list in `initdb.sh`.
## Test plan
- [x] `kubectl --context kind-unbound apply -f k8s/infra/postgres.yaml` — rollout succeeds
- [x] Postgres pod stable (0 restarts) after apply
- [ ] On a fresh cluster (`./setup`), verify the `document` database is created (requires empty `data/postgres/`)
Postgres was OOMKilled repeatedly with the 600Mi limit given
shared_buffers=384MB + max_connections=300. Drop the limit entirely
for the local dev cluster (keep the 400Mi request for scheduling).
Also seed a 'document' database in initdb.sh.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
argoyle
merged commit 73ccafab68 into main2026-04-18 16:34:19 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
shared_buffers=384MB+max_connections=300the pod was being repeatedly OOMKilled under real workloads, leaving clients with intermittentconnect: connection refused. Keep the 400Mi request for scheduling.documentto the seeded database list ininitdb.sh.Test plan
kubectl --context kind-unbound apply -f k8s/infra/postgres.yaml— rollout succeeds./setup), verify thedocumentdatabase is created (requires emptydata/postgres/)