unboundsoftware/local-k8s
6
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Activity

fix(postgres): remove memory limit and add document database #259

Merged
argoyle merged 1 commits from fix-postgres-oom into main 2026-04-18 16:34:19 +00:00
Conversation 0 Commits 1 Files Changed 1
+1 -2
argoyle commented 2026-04-18 16:33:53 +00:00
Owner
Copy Link
Copy Source

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

  • kubectl --context kind-unbound apply -f k8s/infra/postgres.yaml — rollout succeeds
  • Postgres pod stable (0 restarts) after apply
  • 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/`)
argoyle added 1 commit 2026-04-18 16:33:54 +00:00
fix(postgres): remove memory limit and add document database 551cd3b5b5 
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 main 2026-04-18 16:34:19 +00:00
argoyle deleted branch fix-postgres-oom 2026-04-18 16:34:22 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
acctest (Shiny Acctest) argoyle (Joakim Olsson) buildtools (Buildtools) kubernetes (Kubernetes) releaser (Unbound Releaser) renovate (Renovate Bot)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: unboundsoftware/local-k8s#259
Delete Branch "fix-postgres-oom"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?