unboundsoftware/schemas
6
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases 33 Activity

fix: raise Node heap cap to 512MB and bump pod memory limit #838

Merged
argoyle merged 1 commits from bump-wgc-memory into main 2026-05-19 05:20:36 +00:00
Conversation 0 Commits 1 Files Changed 2
+7 -3
1 Commits
Author SHA1 Message Date
argoyle 921d4e39fa fix: raise Node heap cap to 512MB and bump pod memory limit
schemas / vulnerabilities (pull_request) Successful in 2m10s
Details
schemas / check (pull_request) Successful in 2m59s
Details
schemas / check-release (pull_request) Successful in 3m35s
Details
pre-commit / pre-commit (pull_request) Successful in 6m43s
Details
schemas / build (pull_request) Successful in 17m35s
Details
schemas / deploy-prod (pull_request) Has been skipped
Details 
The Dockerfile's NODE_OPTIONS=--max-old-space-size=64 was added to keep
idle Node memory low, but in practice it OOMs wgc router compose as soon
as the supergraph has more than a handful of subgraphs:

  FATAL ERROR: Ineffective mark-compacts near heap limit
  Allocation failed - JavaScript heap out of memory

Bake the higher cap into the image and raise the container memory limit
(k8s/deploy.yaml) so the cgroup doesn't kill the pod at the new ceiling.
Memory request stays modest so the pod still schedules tightly when idle.

The live k8s.unbound.se cluster was already patched in place (kubectl
set env + set resources). This commit makes the manifest match.
 2026-05-19 06:56:12 +02:00